Physical Resource Block Bundling in Multi-TRP Operation

ABSTRACT

Wireless communication systems can include multiple Transmission and Reception Points (TRPs). Systems, devices, and techniques for control signaling of Precoding Resource block Group (PRG) size configuration for multi-TRP operations are described. A described technique includes determining, by a User Equipment (UE), a PRG size based on a downlink control information (DCI) message that provides scheduling information for a physical ?downlink shared channel (PDSCH); receiving, by the UE, a group of PDSCH transmissions from multiple TRPs that are transmitted in accordance with the DCI message; and decoding, by the UE, one or more of the PDSCH transmissions based on the PRG size.

CROSS-REFERENCE TO RELATED APPLICATION

This disclosure claims the benefit of the priority of U.S. ProvisionalPatent Application No. 62/821,338, entitled “PHYSICAL RESOURCE BLOCKBUNDLING IN MULTI-TRP OPERATION” and filed on Mar. 20, 2019. Theabove-identified application is incorporated herein by reference in itsentirety.

TECHNICAL FIELD

This disclosure relates generally to signaling in wireless communicationsystems.

BACKGROUND

Wireless communication systems are rapidly growing in usage. Further,wireless communication technology has evolved from voice-onlycommunications to also include the transmission of data, such asInternet and multimedia content, to a variety of devices. To accommodatea growing number of devices communicating both voice and data signals,many wireless communication systems share the available communicationchannel resources among devices.

SUMMARY

Wireless communication systems can include multiple Transmission andReception Points (TRPs). Systems, devices, and techniques for controlsignaling of Precoding Resource block Group (PRG) size configuration formulti-TRP operations are described. A described technique includesdetermining, by a User Equipment (UE), a PRG size based on a downlinkcontrol information (DCI) message that provides scheduling informationfor a physical downlink shared channel (PDSCH); receiving, by the UE, agroup of PDSCH transmissions from multiple TRPs that are transmitted inaccordance with the DCI message; and decoding, by the UE, one or more ofthe PDSCH transmissions based on the PRG size. Other implementationsinclude corresponding systems, apparatus, and computer programs toperform the actions of methods defined by instructions encoded oncomputer readable storage.

Implementations of any of the above aspects can include one or acombination of two or more of the following features. In someimplementations, the PDSCH transmissions comprise physical resourceblocks (PRBs) that are associated with different transmissionconfiguration indicator (TCI) states, and the multiple TRPs arerespectively associated with the TCI states. The TCI states comprise afirst TCI state and a second TCI state. The PRBs can include a first PRBassociated with a first TCI state and a second PRB associated with asecond TCI state. Determining the PRG size can include determining ifthe first PRB and the second PRB overlap. Determining the PRG size caninclude determining if the PRBs associated with the different TCI statesare non-overlapping or at least partially overlapping. Determining thePRG size can include determining that the PRG size is not wideband ifthe PRBs associated with different TCI states are partially overlappingor non-overlapping.

Implementations can include determining that a precoder for at least oneof the PDSCH transmissions is constant or wideband if PRBs associatedwith different TCI states are non-overlapping. In some implementations,the DCI message is a single DCI message that provides schedulinginformation for the group of PDSCH transmissions. Determining the PRGsize can include determining if a bundle type parameter specifies adynamic bundling attribute. Determining the PRG size can includedetermining if a bundle size set parameter contains two or more bundlesize parameters. Determining the PRG size can include determining if atleast a portion of the PRBs are contiguous. Determining the PRG size caninclude determining whether at least a portion of the PDSCHtransmissions are multiplexed in frequency, space, or both.

In some implementations, the DCI message can include two or more DCImessages that provide scheduling information for the group of PDSCHtransmissions. In some implementations, the PDSCH transmissions includePRBs that are associated with different TCI states. The multiple TRPscan be respectively associated with the TCI states. Determining the PRGsize can include determining if a bundle type parameter specifies adynamic bundling attribute.

In some implementations, determining the PRG size can includedetermining that a PRG size is equal to wideband based on the two ormore DCI messages. Determining that the PRG size is equal to widebandcan include determining whether a bandwidth of a total number of PRBsscheduled by the two or more DCI messages is above half of a bandwidthof an active bandwidth part.

A UE, in some implementations, can include one or more processors;circuitry configured to receive information including a DCI message thatprovides scheduling information for a PDSCH, and a group of PDSCHtransmissions from multiple TRPs that are transmitted in accordance withthe DCI message; and a memory storing instructions that, when executedby the one or more processors, cause the one or more processors toperform operations. The operations can include determining a PRG sizebased on the DCI message; and decoding one or more of the PDSCHtransmissions based on the PRG size.

The details of one or more implementations are set forth in theaccompanying drawings and the description below. Other features andadvantages will be apparent from the description and drawings, and fromthe claims.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 illustrates an example of a wireless communication system.

FIG. 2 illustrates an example architecture of a system including a corenetwork.

FIG. 3 illustrates another example architecture of a system including acore network.

FIG. 4 illustrates an example of infrastructure equipment.

FIG. 5 illustrates an example of a platform or device.

FIG. 6 illustrates example components of baseband circuitry and radiofront end circuitry.

FIG. 7 illustrates example components of cellular communicationcircuitry.

FIG. 8 illustrates example protocol functions that may be implemented inwireless communication systems.

FIG. 9 illustrates an example of a computer system.

FIG. 10 illustrates a flowchart of an example procedure for deriving aPRG size.

FIG. 11 illustrates an example of a multi-TRP operation.

FIG. 12 illustrates a flowchart of an example of a decoding processassociated with a multi-TRP operation.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

In addition to transmitting user data, base stations can provide controlsignaling to user devices. Various types of control signals includesscheduling information and decoding information. A user device can usethe scheduling information and decoding information to receive anddecode user data. In some implementations, multiple base stations cantransmit data to the same user device. The user's data can bemultiplexed in time, space, frequency, or a combination thereof. In someimplementations, each base station corresponds to a Transmission andReception Point (TRP). In some implementations, a base station can havetwo or more TRPs.

FIG. 1 illustrates an example of a wireless communication system 100.For purposes of convenience and without limitation, the example system100 is described in the context of the LTE and 5G NR communicationstandards as defined by the Third Generation Partnership Project (3GPP)technical specifications. However, other types of communicationstandards are possible.

The system 100 includes UE 101 a and UE 101 b (collectively referred toas the “UEs 101”). In this example, the UEs 101 are illustrated assmartphones (e.g., handheld touchscreen mobile computing devicesconnectable to one or more cellular networks). In other examples, any ofthe UEs 101 can include other mobile or non-mobile computing devices,such as consumer electronics devices, cellular phones, smartphones,feature phones, tablet computers, wearable computer devices, personaldigital assistants (PDAs), pagers, wireless handsets, desktop computers,laptop computers, in-vehicle infotainment (IVI), in-car entertainment(ICE) devices, an Instrument Cluster (IC), head-up display (HUD)devices, onboard diagnostic (OBD) devices, dashtop mobile equipment(DME), mobile data terminals (MDTs), Electronic Engine Management System(EEMS), electronic/engine control units (ECUs), electronic/enginecontrol modules (ECMs), embedded systems, microcontrollers, controlmodules, engine management systems (EMS), networked or “smart”appliances, machine-type communications (MTC) devices,machine-to-machine (M2M) devices, Internet of Things (IoT) devices, orcombinations of them, among others.

In some implementations, any of the UEs 101 may be IoT UEs, which caninclude a network access layer designed for low-power IoT applicationsutilizing short-lived UE connections. An IoT UE can utilize technologiessuch as M2M or MTC for exchanging data with an MTC server or deviceusing, for example, a public land mobile network (PLMN), proximityservices (ProSe), device-to-device (D2D) communication, sensor networks,IoT networks, or combinations of them, among others. The M2M or MTCexchange of data may be a machine-initiated exchange of data. An IoTnetwork describes interconnecting IoT UEs, which can include uniquelyidentifiable embedded computing devices (within the Internetinfrastructure), with short-lived connections. The IoT UEs may executebackground applications (e.g., keep-alive messages or status updates) tofacilitate the connections of the IoT network.

The UEs 101 are configured to connect (e.g., communicatively couple)with an access network (AN) or radio access network (RAN) 110. In someimplementations, the RAN 110 may be a next generation RAN (NG RAN), anevolved UMTS terrestrial radio access network (E-UTRAN), or a legacyRAN, such as a UMTS terrestrial radio access network (UTRAN) or a GSMEDGE radio access network (GERAN). As used herein, the term “NG RAN” mayrefer to a RAN 110 that operates in a 5G NR system 100, and the term“E-UTRAN” may refer to a RAN 110 that operates in an LTE or 4G system100.

To connect to the RAN 110, the UEs 101 utilize connections (or channels)103 and 104, respectively, each of which can include a physicalcommunications interface or layer, as described below. In this example,the connections 103 and 104 are illustrated as an air interface toenable communicative coupling, and can be consistent with cellularcommunications protocols, such as a global system for mobilecommunications (GSM) protocol, a code-division multiple access (CDMA)network protocol, a push-to-talk (PTT) protocol, a PTT over cellular(POC) protocol, a universal mobile telecommunications system (UMTS)protocol, a 3GPP LTE protocol, a 5G NR protocol, or combinations ofthem, among other communication protocols.

The RAN 110 can include one or more AN nodes or RAN nodes 111 a and 111b (collectively referred to as “RAN nodes 111” or “RAN node 111”) thatenable the connections 103 and 104. As used herein, the terms “accessnode,” “access point,” or the like may describe equipment that providesthe radio baseband functions for data or voice connectivity, or both,between a network and one or more users. These access nodes can bereferred to as base stations (BS), gNodeBs, gNBs, eNodeBs, eNBs, NodeBs,RAN nodes, rode side units (RSUs), and the link, and can include groundstations (e.g., terrestrial access points) or satellite stationsproviding coverage within a geographic area (e.g., a cell), amongothers. As used herein, the term “NG RAN node” may refer to a RAN node111 that operates in an 5G NR system 100 (for example, a gNB), and theterm “E-UTRAN node” may refer to a RAN node 111 that operates in an LTEor 4G system 100 (e.g., an eNB). In some implementations, the RAN nodes111 may be implemented as one or more of a dedicated physical devicesuch as a macrocell base station, or a low power (LP) base station forproviding femtocells, picocells or other like cells having smallercoverage areas, smaller user capacity, or higher bandwidth compared tomacrocells.

Any of the RAN nodes 111 can terminate the air interface protocol andcan be the first point of contact for the UEs 101. In someimplementations, any of the RAN nodes 111 can fulfill various logicalfunctions for the RAN 110 including, but not limited to, radio networkcontroller (RNC) functions such as radio bearer management, uplink anddownlink dynamic radio resource management and data packet scheduling,and mobility management.

In some implementations, the UEs 101 can be configured to communicateusing orthogonal frequency division multiplexing (OFDM) communicationsignals with each other or with any of the RAN nodes 111 over amulticarrier communication channel in accordance with variouscommunication techniques, such as, but not limited to, OFDMAcommunication techniques (e.g., for downlink communications) or SC-FDMAcommunication techniques (e.g., for uplink communications), although thescope of the techniques described here not limited in this respect. TheOFDM signals can comprise a plurality of orthogonal subcarriers.

The RAN nodes 111 can transmit to the UEs 101 over various channels.Various examples of downlink communication channels include PhysicalBroadcast Channel (PBCH), Physical Downlink Control Channel (PDCCH), andPhysical Downlink Shared Channel (PDSCH). Other types of downlinkchannels are possible. The UEs 101 can transmit to the RAN nodes 111over various channels. Various examples of uplink communication channelsinclude Physical Uplink Shared Channel (PUSCH), Physical Uplink ControlChannel (PUCCH), and Physical Random Access Channel (PRACH). Other typesof uplink channels are possible.

In some implementations, a downlink resource grid can be used fordownlink transmissions from any of the RAN nodes 111 to the UEs 101,while uplink transmissions can utilize similar techniques. The grid canbe a frequency grid or a time-frequency grid, which is the physicalresource in the downlink in each slot. Such a time-frequency planerepresentation is a common practice for OFDM systems, which makes itintuitive for radio resource allocation. Each column and each row of theresource grid corresponds to one OFDM symbol and one OFDM subcarrier,respectively. The duration of the resource grid in the time domaincorresponds to one slot in a radio frame. The smallest time-frequencyunit in a resource grid is denoted as a resource element. Each resourcegrid comprises a number of resource blocks, which describe the mappingof certain physical channels to resource elements. Each resource blockcomprises a collection of resource elements; in the frequency domain,this may represent the smallest quantity of resources that currently canbe allocated. There are several different physical downlink channelsthat are conveyed using such resource blocks. In some implementations, aphysical resource block (PRB) can include a number of resource blocks. APCB can be used as a unit in a frequency-domain resource allocation forchannels such as PDSCH.

The PDSCH carries user data and higher-layer signaling to the UEs 101.The PDCCH carries information about the transport format and resourceallocations related to the PDSCH channel, among other things. It mayalso inform the UEs 101 about the transport format, resource allocation,and hybrid automatic repeat request (HARM) information related to theuplink shared channel. Downlink scheduling (e.g., assigning control andshared channel resource blocks to the UE 101 b within a cell) may beperformed at any of the RAN nodes 111 based on channel qualityinformation fed back from any of the UEs 101. The downlink resourceassignment information may be sent on the PDCCH used for (e.g., assignedto) each of the UEs 101.

The PDCCH can convey scheduling information of different types.Scheduling information can include downlink resource scheduling, uplinkpower control instructions, uplink resource grants, and indications forpaging or system information. The RAN nodes 111 can transmit one or moredownlink control information (DCI) messages on the PDCCH to providescheduling information, such as allocations of one or more PRBs.

In some implementations, the PDCCH uses control channel elements (CCEs)to convey the control information. Before being mapped to resourceelements, the PDCCH complex-valued symbols may first be organized intoquadruplets, which may then be permuted using a sub-block interleaverfor rate matching. In some implementations, each PDCCH may betransmitted using one or more of these CCEs, in which each CCE maycorrespond to nine sets of four physical resource elements collectivelyreferred to as resource element groups (REGs). Four Quadrature PhaseShift Keying (QPSK) symbols may be mapped to each REG. The PDCCH can betransmitted using one or more CCEs, depending on the size of DCI and thechannel condition. In some implementations, there can be four or moredifferent PDCCH formats defined with different numbers of CCEs (e.g.,aggregation level, L=1, 2, 4, or 8).

The RAN nodes 111 are configured to communicate with one another usingan interface 112. In examples, such as where the system 100 is an LTEsystem (e.g., when the core network 120 is an evolved packet core (EPC)network as shown in FIG. 2), the interface 112 may be an X2 interface112. The X2 interface may be defined between two or more RAN nodes 111(e.g., two or more eNBs and the like) that connect to the EPC 120, orbetween two eNBs connecting to EPC 120, or both. In someimplementations, the X2 interface can include an X2 user plane interface(X2-U) and an X2 control plane interface (X2-C). The X2-U may provideflow control mechanisms for user data packets transferred over the X2interface, and may be used to communicate information about the deliveryof user data between eNBs. For example, the X2-U may provide specificsequence number information for user data transferred from a master eNBto a secondary eNB; information about successful in sequence delivery ofPDCP protocol data units (PDUs) to a UE 101 from a secondary eNB foruser data; information of PDCP PDUs that were not delivered to a UE 101;information about a current minimum desired buffer size at the secondaryeNB for transmitting to the UE user data, among other information. TheX2-C may provide intra-LTE access mobility functionality, includingcontext transfers from source to target eNBs or user plane transportcontrol; load management functionality; inter-cell interferencecoordination functionality, among other functionality.

In some implementations, such as where the system 100 is a 5G NR system(e.g., when the core network 120 is a 5G core network as shown in FIG.3), the interface 112 may be an Xn interface 112. The Xn interface maybe defined between two or more RAN nodes 111 (e.g., two or more gNBs andthe like) that connect to the 5G core network 120, between a RAN node111 (e.g., a gNB) connecting to the 5G core network 120 and an eNB, orbetween two eNBs connecting to the 5G core network 120, or combinationsof them. In some implementations, the Xn interface can include an Xnuser plane (Xn-U) interface and an Xn control plane (Xn-C) interface.The Xn-U may provide non-guaranteed delivery of user plane PDUs andsupport/provide data forwarding and flow control functionality. The Xn-Cmay provide management and error handling functionality, functionalityto manage the Xn-C interface; mobility support for UE 101 in a connectedmode (e.g., CM-CONNECTED) including functionality to manage the UEmobility for connected mode between one or more RAN nodes 111, amongother functionality. The mobility support can include context transferfrom an old (source) serving RAN node 111 to new (target) serving RANnode 111, and control of user plane tunnels between old (source) servingRAN node 111 to new (target) serving RAN node 111. A protocol stack ofthe Xn-U can include a transport network layer built on InternetProtocol (IP) transport layer, and a GPRS tunneling protocol for userplane (GTP-U) layer on top of a user datagram protocol (UDP) or IPlayer(s), or both, to carry user plane PDUs. The Xn-C protocol stack caninclude an application layer signaling protocol (referred to as XnApplication Protocol (Xn-AP or XnAP)) and a transport network layer thatis built on a stream control transmission protocol (SCTP). The SCTP maybe on top of an IP layer, and may provide the guaranteed delivery ofapplication layer messages. In the transport IP layer, point-to-pointtransmission is used to deliver the signaling PDUs. In otherimplementations, the Xn-U protocol stack or the Xn-C protocol stack, orboth, may be same or similar to the user plane and/or control planeprotocol stack(s) shown and described herein.

The RAN 110 is shown to be communicatively coupled to a core network 120(referred to as a “CN 120”). The CN 120 includes one or more networkelements 122, which are configured to offer various data andtelecommunications services to customers/subscribers (e.g., users of UEs101) who are connected to the CN 120 using the RAN 110. The componentsof the CN 120 may be implemented in one physical node or separatephysical nodes and can include components to read and executeinstructions from a machine-readable or computer-readable medium (e.g.,a non-transitory machine-readable storage medium). In someimplementations, network functions virtualization (NFV) may be used tovirtualize some or all of the network node functions described hereusing executable instructions stored in one or more computer-readablestorage mediums, as described in further detail below. A logicalinstantiation of the CN 120 may be referred to as a network slice, and alogical instantiation of a portion of the CN 120 may be referred to as anetwork sub-slice. NFV architectures and infrastructures may be used tovirtualize one or more network functions, alternatively performed byproprietary hardware, onto physical resources comprising a combinationof industry-standard server hardware, storage hardware, or switches. Inother words, NFV systems can be used to execute virtual orreconfigurable implementations of one or more network components orfunctions, or both.

An application server 130 may be an element offering applications thatuse IP bearer resources with the core network (e.g., UMTS packetservices (PS) domain, LTE PS data services, among others). Theapplication server 130 can also be configured to support one or morecommunication services (e.g., VoIP sessions, PTT sessions, groupcommunication sessions, social networking services, among others) forthe UEs 101 using the CN 120. The application server 130 can use an IPcommunications interface 125 to communicate with one or more networkelements 112.

In some implementations, the CN 120 may be a 5G core network (referredto as “5GC 120” or “5G core network 120”), and the RAN 110 may beconnected with the CN 120 using a next generation interface 113. In someimplementations, the next generation interface 113 may be split into twoparts, an next generation user plane (NG-U) interface 114, which carriestraffic data between the RAN nodes 111 and a user plane function (UPF),and the S1 control plane (NG-C) interface 115, which is a signalinginterface between the RAN nodes 111 and access and mobility managementfunctions (AMFs). Examples where the CN 120 is a 5G core network arediscussed in more detail with regard to FIG. 3.

In some implementations, the CN 120 may be an EPC (referred to as “EPC120” or the like), and the RAN 110 may be connected with the CN 120using an S1 interface 113. In some implementations, the S1 interface 113may be split into two parts, an S1 user plane (S1-U) interface 114,which carries traffic data between the RAN nodes 111 and the servinggateway (S-GW), and the S1-MME interface 115, which is a signalinginterface between the RAN nodes 111 and mobility management entities(MMEs).

In some implementations, the UEs 101 may directly exchange communicationdata using an interface 105, such as a ProSe interface. The interface105 may alternatively be referred to as a sidelink interface 105 and caninclude one or more logical channels, such as a physical sidelinkcontrol channel (PSCCH), a physical sidelink shared channel (PSSCH), aphysical sidelink downlink channel (PSDCH), or a physical sidelinkbroadcast channel (PSBCH), or combinations of them, among others.

The UE 101 b is shown to be configured to access an access point (AP)106 (also referred to as “WLAN node 106,” “WLAN 106,” “WLAN Termination106,” “WT 106” or the like) using a connection 107. The connection 107can include a local wireless connection, such as a connection consistentwith any IEEE 802.11 protocol, in which the AP 106 would include awireless fidelity (Wi-Fi) router. In this example, the AP 106 is shownto be connected to the Internet without connecting to the core networkof the wireless system, as described in further detail below. In variousexamples, the UE 101 b, RAN 110, and AP 106 may be configured to useLTE-WLAN aggregation (LWA) operation or LTW/WLAN radio level integrationwith IPsec tunnel (LWIP) operation. The LWA operation may involve the UE101 b in RRC_CONNECTED being configured by a RAN node 111 a, 111 b toutilize radio resources of LTE and WLAN. LWIP operation may involve theUE 101 b using WLAN radio resources (e.g., connection 107) using IPsecprotocol tunneling to authenticate and encrypt packets (e.g., IPpackets) sent over the connection 107. IPsec tunneling can includeencapsulating the entirety of original IP packets and adding a newpacket header, thereby protecting the original header of the IP packets.

In some implementations, some or all of the RAN nodes 111 may beimplemented as one or more software entities running on server computersas part of a virtual network, which may be referred to as a cloud RAN(CRAN) or a virtual baseband unit pool (vBBUP). The CRAN or vBBUP mayimplement a RAN function split, such as a packet data convergenceprotocol (PDCP) split in which radio resource control (RRC) and PDCPlayers are operated by the CRAN/vBBUP and other layer two (e.g., datalink layer) protocol entities are operated by individual RAN nodes 111;a medium access control (MAC)/physical layer (PHY) split in which RRC,PDCP, MAC, and radio link control (RLC) layers are operated by theCRAN/vBBUP and the PHY layer is operated by individual RAN nodes 111; ora “lower PHY” split in which RRC, PDCP, RLC, and MAC layers and upperportions of the PHY layer are operated by the CRAN/vBBUP and lowerportions of the PHY layer are operated by individual RAN nodes 111. Thisvirtualized framework allows the freed-up processor cores of the RANnodes 111 to perform, for example, other virtualized applications. Insome implementations, an individual RAN node 111 may representindividual gNB distributed units (DUs) that are connected to a gNBcentral unit (CU) using individual F1 interfaces (not shown in FIG. 1).In some implementations, the gNB-DUs can include one or more remoteradio heads or RFEMs (see, e.g., FIG. 4), and the gNB-CU may be operatedby a server that is located in the RAN 110 (not shown) or by a serverpool in a similar manner as the CRAN/vBBUP. Additionally oralternatively, one or more of the RAN nodes 111 may be next generationeNBs (ng-eNBs), including RAN nodes that provide E-UTRA user plane andcontrol plane protocol terminations toward the UEs 101, and areconnected to a 5G core network (e.g., core network 120) using a nextgeneration interface.

In vehicle-to-everything (V2X) scenarios, one or more of the RAN nodes111 may be or act as RSUs. The term “Road Side Unit” or “RSU” refers toany transportation infrastructure entity used for V2X communications. ARSU may be implemented in or by a suitable RAN node or a stationary (orrelatively stationary) UE, where a RSU implemented in or by a UE may bereferred to as a “UE-type RSU,” a RSU implemented in or by an eNB may bereferred to as an “eNB-type RSU,” a RSU implemented in or by a gNB maybe referred to as a “gNB-type RSU,” and the like. In someimplementations, an RSU is a computing device coupled with radiofrequency circuitry located on a roadside that provides connectivitysupport to passing vehicle UEs 101 (vUEs 101). The RSU may also includeinternal data storage circuitry to store intersection map geometry,traffic statistics, media, as well as applications or other software tosense and control ongoing vehicular and pedestrian traffic. The RSU mayoperate on the 5.9 GHz Direct Short Range Communications (DSRC) band toprovide very low latency communications required for high speed events,such as crash avoidance, traffic warnings, and the like. Additionally oralternatively, the RSU may operate on the cellular V2X band to providethe aforementioned low latency communications, as well as other cellularcommunications services. Additionally or alternatively, the RSU mayoperate as a Wi-Fi hotspot (2.4 GHz band) or provide connectivity to oneor more cellular networks to provide uplink and downlink communications,or both. The computing device(s) and some or all of the radiofrequencycircuitry of the RSU may be packaged in a weatherproof enclosuresuitable for outdoor installation, and can include a network interfacecontroller to provide a wired connection (e.g., Ethernet) to a trafficsignal controller or a backhaul network, or both.

FIG. 2 illustrates an example architecture of a system 200 including afirst CN 220. In this example, the system 200 may implement the LTEstandard such that the CN 220 is an EPC 220 that corresponds with CN 120of FIG. 1. Additionally, the UE 201 may be the same or similar as theUEs 101 of FIG. 1, and the E-UTRAN 210 may be a RAN that is the same orsimilar to the RAN 110 of FIG. 1, and which can include RAN nodes 111discussed previously. The CN 220 may comprise MMEs 221, an S-GW 222, aPDN gateway (P-GW) 223, a high-speed packet access (HSS) function 224,and a serving GPRS support node (SGSN) 225.

The MMEs 221 may be similar in function to the control plane of legacySGSN, and may implement mobility management (MM) functions to keep trackof the current location of a UE 201. The MMEs 221 may perform variousmobility management procedures to manage mobility aspects in access suchas gateway selection and tracking area list management. Mobilitymanagement (also referred to as “EPS MM” or “EMM” in E-UTRAN systems)may refer to all applicable procedures, methods, data storage, and otheraspects that are used to maintain knowledge about a present location ofthe UE 201, provide user identity confidentiality, or perform other likeservices to users/subscribers, or combinations of them, among others.Each UE 201 and the MME 221 can include an EMM sublayer, and an mobilitymanagement context may be established in the UE 201 and the MME 221 whenan attach procedure is successfully completed. The mobility managementcontext may be a data structure or database object that stores mobilitymanagement-related information of the UE 201. The MMEs 221 may becoupled with the HSS 224 using a S6a reference point, coupled with theSGSN 225 using a S3 reference point, and coupled with the S-GW 222 usinga S11 reference point.

The SGSN 225 may be a node that serves the UE 201 by tracking thelocation of an individual UE 201 and performing security functions. Inaddition, the SGSN 225 may perform Inter-EPC node signaling for mobilitybetween 2G/3G and E-UTRAN 3GPP access networks; PDN and S-GW selectionas specified by the MMEs 221; handling of UE 201 time zone functions asspecified by the MMEs 221; and MME selection for handovers to E-UTRAN3GPP access network, among other functions. The S3 reference pointbetween the MMEs 221 and the SGSN 225 may enable user and bearerinformation exchange for inter-3GPP access network mobility in idle oractive states, or both.

The HSS 224 can include a database for network users, includingsubscription-related information to support the network entities'handling of communication sessions. The EPC 220 can include one or moreHSSs 224 depending on the number of mobile subscribers, on the capacityof the equipment, on the organization of the network, or combinations ofthem, among other features. For example, the HSS 224 can provide supportfor routing, roaming, authentication, authorization, naming/addressingresolution, location dependencies, among others. A S6a reference pointbetween the HSS 224 and the MMEs 221 may enable transfer of subscriptionand authentication data for authenticating or authorizing user access tothe EPC 220 between HSS 224 and the MMEs 221.

The S-GW 222 may terminate the S1 interface 113 (“S1-U” in FIG. 2)toward the RAN 210, and may route data packets between the RAN 210 andthe EPC 220. In addition, the S-GW 222 may be a local mobility anchorpoint for inter-RAN node handovers and also may provide an anchor forinter-3GPP mobility. Other responsibilities can include lawfulintercept, charging, and some policy enforcement. The S11 referencepoint between the S-GW 222 and the MMEs 221 may provide a control planebetween the MMEs 221 and the S-GW 222. The S-GW 222 may be coupled withthe P-GW 223 using a S5 reference point.

The P-GW 223 may terminate a SGi interface toward a PDN 230. The P-GW223 may route data packets between the EPC 220 and external networkssuch as a network including the application server 130 (sometimesreferred to as an “AF”) using an IP communications interface 125 (see,e.g., FIG. 1). In some implementations, the P-GW 223 may becommunicatively coupled to an application server (e.g., the applicationserver 130 of FIG. 1 or PDN 230 in FIG. 2) using an IP communicationsinterface 125 (see, e.g., FIG. 1). The S5 reference point between theP-GW 223 and the S-GW 222 may provide user plane tunneling and tunnelmanagement between the P-GW 223 and the S-GW 222. The S5 reference pointmay also be used for S-GW 222 relocation due to UE 201 mobility and ifthe S-GW 222 needs to connect to a non-collocated P-GW 223 for therequired PDN connectivity. The P-GW 223 may further include a node forpolicy enforcement and charging data collection (e.g., PCEF (notshown)). Additionally, the SGi reference point between the P-GW 223 andthe packet data network (PDN) 230 may be an operator external public, aprivate PDN, or an intra operator packet data network, for example, forprovision of IMS services. The P-GW 223 may be coupled with a policycontrol and charging rules function (PCRF) 226 using a Gx referencepoint.

PCRF 226 is the policy and charging control element of the EPC 220. In anon-roaming scenario, there may be a single PCRF 226 in the Home PublicLand Mobile Network (HPLMN) associated with a UE 201's Internet ProtocolConnectivity Access Network (IP-CAN) session. In a roaming scenario withlocal breakout of traffic, there may be two PCRFs associated with a UE201's IP-CAN session, a Home PCRF (H-PCRF) within an HPLMN and a VisitedPCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). ThePCRF 226 may be communicatively coupled to the application server 230using the P-GW 223. The application server 230 may signal the PCRF 226to indicate a new service flow and select the appropriate quality ofservice (QoS) and charging parameters. The PCRF 226 may provision thisrule into a PCEF (not shown) with the appropriate traffic flow template(TFT) and QoS class identifier (QCI), which commences the QoS andcharging as specified by the application server 230. The Gx referencepoint between the PCRF 226 and the P-GW 223 may allow for the transferof QoS policy and charging rules from the PCRF 226 to PCEF in the P-GW223. A Rx reference point may reside between the PDN 230 (or “AF 230”)and the PCRF 226.

FIG. 3 illustrates an architecture of a system 300 including a second CN320. The system 300 is shown to include a UE 301, which may be the sameor similar to the UEs 101 and UE 201 discussed previously; a (R)AN 310,which may be the same or similar to the RAN 110 and RAN 210 discussedpreviously, and which can include RAN nodes 111 discussed previously;and a data network (DN) 303, which may be, for example, operatorservices, Internet access or 3rd party services; and a 5GC 320. The 5GC320 can include an authentication server function (AUSF) 322; an accessand mobility management function (AMF) 321; a session managementfunction (SMF) 324; a network exposure function (NEF) 323; a policycontrol function (PCF) 326; a network repository function (NRF) 325; aunified data management (UDM) function 327; an AF 328; a user planefunction (UPF) 302; and a network slice selection function (NSSF) 329.

The UPF 302 may act as an anchor point for intra-RAT and inter-RATmobility, an external PDU session point of interconnect to DN 303, and abranching point to support multi-homed PDU session. The UPF 302 may alsoperform packet routing and forwarding, perform packet inspection,enforce the user plane part of policy rules, lawfully intercept packets(UP collection), perform traffic usage reporting, perform QoS handlingfor a user plane (e.g., packet filtering, gating, UL/DL rateenforcement), perform Uplink Traffic verification (e.g., SDF to QoS flowmapping), transport level packet marking in the uplink and downlink, andperform downlink packet buffering and downlink data notificationtriggering. UPF 302 can include an uplink classifier to support routingtraffic flows to a data network. The DN 303 may represent variousnetwork operator services, Internet access, or third party services. DN303 can include, or be similar to, application server 130 discussedpreviously. The UPF 302 may interact with the SMF 324 using a N4reference point between the SMF 324 and the UPF 302.

The AUSF 322 stores data for authentication of UE 301 and handleauthentication-related functionality. The AUSF 322 may facilitate acommon authentication framework for various access types. The AUSF 322may communicate with the AMF 321 using a N12 reference point between theAMF 321 and the AUSF 322, and may communicate with the UDM 327 using aN13 reference point between the UDM 327 and the AUSF 322. Additionally,the AUSF 322 may exhibit a Nausf service-based interface.

The AMF 321 is responsible for registration management (e.g., forregistering UE 301), connection management, reachability management,mobility management, and lawful interception of AMF-related events, andaccess authentication and authorization. The AMF 321 may be atermination point for the N11 reference point between the AMF 321 andthe SMF 324. The AMF 321 may provide transport for SM messages betweenthe UE 301 and the SMF 324, and act as a transparent pro10 for routingSM messages. AMF 321 may also provide transport for SMS messages betweenUE 301 and an SMSF (not shown in FIG. 3). AMF 321 may act as securityanchor function (SEAF), which can include interaction with the AUSF 322and the UE 301 to, for example, receive an intermediate key that wasestablished as a result of the UE 301 authentication process. Whereuniversal subscriber identity module (USIM) based authentication isused, the AMF 321 may retrieve the security material from the AUSF 322.AMF 321 may also include a security context management (SCM) function,which receives a key from the SEAF to derive access-network specifickeys. Furthermore, AMF 321 may be a termination point of a RAN controlplane interface, which can include or be a N2 reference point betweenthe (R)AN 310 and the AMF 321. In some implementations, the AMF 321 maybe a termination point of NAS (N1) signaling and perform NAS cipheringand integrity protection.

AMF 321 may also support NAS signaling with a UE 301 over a N3inter-working function (IWF) interface (referred to as the “N3IWF”). TheN3IWF may be used to provide access to untrusted entities. The N3IWF maybe a termination point for the N2 interface between the (R)AN 310 andthe AMF 321 for the control plane, and may be a termination point forthe N3 reference point between the (R)AN 310 and the UPF 302 for theuser plane. As such, the AMF 321 may handle N2 signaling from the SMF324 and the AMF 321 for PDU sessions and QoS, encapsulate/de-encapsulatepackets for IPsec and N3 tunneling, mark N3 user-plane packets in theuplink, and enforce QoS corresponding to N3 packet marking taking intoaccount QoS requirements associated with such marking received over N2.The N3IWF may also relay uplink and downlink control-plane NAS signalingbetween the UE 301 and AMF 321 using a N1 reference point between the UE301 and the AMF 321, and relay uplink and downlink user-plane packetsbetween the UE 301 and UPF 302. The N3IWF also provides mechanisms forIPsec tunnel establishment with the UE 301. The AMF 321 may exhibit aNamf service-based interface, and may be a termination point for a N14reference point between two AMFs 321 and a N17 reference point betweenthe AMF 321 and a 5G equipment identity registry (EIR) (not shown inFIG. 3).

The UE 301 may register with the AMF 321 in order to receive networkservices. Registration management (RM) is used to register or deregisterthe UE 301 with the network (e.g., AMF 321), and establish a UE contextin the network (e.g., AMF 321). The UE 301 may operate in aRM-REGISTERED state or an RM-DEREGISTERED state. In the RM DEREGISTEREDstate, the UE 301 is not registered with the network, and the UE contextin AMF 321 holds no valid location or routing information for the UE 301so the UE 301 is not reachable by the AMF 321. In the RM REGISTEREDstate, the UE 301 is registered with the network, and the UE context inAMF 321 may hold a valid location or routing information for the UE 301so the UE 301 is reachable by the AMF 321. In the RM-REGISTERED state,the UE 301 may perform mobility Registration Update procedures, performperiodic Registration Update procedures triggered by expiration of theperiodic update timer (e.g., to notify the network that the UE 301 isstill active), and perform a Registration Update procedure to update UEcapability information or to re-negotiate protocol parameters with thenetwork, among others.

The AMF 321 may store one or more RM contexts for the UE 301, where eachRM context is associated with a specific access to the network. The RMcontext may be, for example, a data structure or database object, amongothers, that indicates or stores a registration state per access typeand the periodic update timer. The AMF 321 may also store a 5GC mobilitymanagement (MM) context that may be the same or similar to the (E)MMcontext discussed previously. In some implementations, the AMF 321 maystore a coverage enhancement mode B Restriction parameter of the UE 301in an associated MM context or RM context. The AMF 321 may also derivethe value, when needed, from the UE's usage setting parameter alreadystored in the UE context (and/or MM/RM context).

Connection management (CM) may be used to establish and release asignaling connection between the UE 301 and the AMF 321 over the N1interface. The signaling connection is used to enable NAS signalingexchange between the UE 301 and the CN 320, and includes both thesignaling connection between the UE and the AN (e.g., RRC connection orUE-N3IWF connection for non-3GPP access) and the N2 connection for theUE 301 between the AN (e.g., RAN 310) and the AMF 321. In someimplementations, the UE 301 may operate in one of two CM modes: CM-IDLEmode or CM-CONNECTED mode. When the UE 301 is operating in the CM-IDLEmode, the UE 301 may have no NAS signaling connection established withthe AMF 321 over the N1 interface, and there may be (R)AN 310 signalingconnection (e.g., N2 or N3 connections, or both) for the UE 301. Whenthe UE 301 is operating in the CM-CONNECTED mode, the UE 301 may have anestablished NAS signaling connection with the AMF 321 over the N1interface, and there may be a (R)AN 310 signaling connection (e.g., N2and/or N3 connections) for the UE 301. Establishment of a N2 connectionbetween the (R)AN 310 and the AMF 321 may cause the UE 301 to transitionfrom the CM-IDLE mode to the CM-CONNECTED mode, and the UE 301 maytransition from the CM-CONNECTED mode to the CM-IDLE mode when N2signaling between the (R)AN 310 and the AMF 321 is released.

The SMF 324 may be responsible for session management (SM), such assession establishment, modify and release, including tunnel maintainbetween UPF and AN node; UE IP address allocation and management(including optional authorization); selection and control of UPfunction; configuring traffic steering at the UPF to route traffic toproper destination; termination of interfaces toward policy controlfunctions; controlling part of policy enforcement and QoS; lawfulintercept (for SM events and interface to LI system); termination of SMparts of NAS messages; downlink data notification; initiating ANspecific SM information, sent using AMF over N2 to AN; and determiningSSC mode of a session. SM may refer to management of a PDU session, anda PDU session (or “session”) may refer to a PDU connectivity servicethat provides or enables the exchange of PDUs between a UE 301 and adata network (DN) 303 identified by a Data Network Name (DNN). PDUsessions may be established upon UE 301 request, modified upon UE 301and 5GC 320 request, and released upon UE 301 and 5GC 320 request usingNAS SM signaling exchanged over the N1 reference point between the UE301 and the SMF 324. Upon request from an application server, the 5GC320 may trigger a specific application in the UE 301. In response toreceipt of the trigger message, the UE 301 may pass the trigger message(or relevant parts/information of the trigger message) to one or moreidentified applications in the UE 301. The identified application(s) inthe UE 301 may establish a PDU session to a specific DNN. The SMF 324may check whether the UE 301 requests are compliant with usersubscription information associated with the UE 301. In this regard, theSMF 324 may retrieve and/or request to receive update notifications onSMF 324 level subscription data from the UDM 327.

The SMF 324 can include some or all of the following roamingfunctionality: handling local enforcement to apply QoS service levelagreements (SLAs) (e.g., in VPLMN); charging data collection andcharging interface (e.g., in VPLMN); lawful intercept (e.g., in VPLMNfor SM events and interface to LI system); and support for interactionwith external DN for transport of signaling for PDU sessionauthorization/authentication by external DN. A N16 reference pointbetween two SMFs 324 may be included in the system 300, which may bebetween another SMF 324 in a visited network and the SMF 324 in the homenetwork in roaming scenarios. Additionally, the SMF 324 may exhibit theNsmf service-based interface.

The NEF 323 may provide means for securely exposing the services andcapabilities provided by 3GPP network functions for third party,internal exposure/re-exposure, Application Functions (e.g., AF 328),edge computing or fog computing systems, among others. In someimplementations, the NEF 323 may authenticate, authorize, and/orthrottle the AFs. The NEF 323 may also translate information exchangedwith the AF 328 and information exchanged with internal networkfunctions. For example, the NEF 323 may translate between anAF-Service-Identifier and an internal 5GC information. NEF 323 may alsoreceive information from other network functions (NFs) based on exposedcapabilities of other network functions. This information may be storedat the NEF 323 as structured data, or at a data storage NF usingstandardized interfaces. The stored information can then be re-exposedby the NEF 323 to other NFs and AFs, or used for other purposes such asanalytics, or both. Additionally, the NEF 323 may exhibit a Nnefservice-based interface.

The NRF 325 may support service discovery functions, receive NFdiscovery requests from NF instances, and provide the information of thediscovered NF instances to the NF instances. NRF 325 also maintainsinformation of available NF instances and their supported services. Asused herein, the terms “instantiate,” “instantiation,” and the like mayrefer to the creation of an instance, and an “instance” may refer to aconcrete occurrence of an object, which may occur, for example, duringexecution of program code. Additionally, the NRF 325 may exhibit theNnrf service-based interface.

The PCF 326 may provide policy rules to control plane function(s) toenforce them, and may also support unified policy framework to governnetwork behavior. The PCF 326 may also implement a front end to accesssubscription information relevant for policy decisions in a unified datarepository (UDR) of the UDM 327. The PCF 326 may communicate with theAMF 321 using an N15 reference point between the PCF 326 and the AMF321, which can include a PCF 326 in a visited network and the AMF 321 incase of roaming scenarios. The PCF 326 may communicate with the AF 328using a N5 reference point between the PCF 326 and the AF 328; and withthe SMF 324 using a N7 reference point between the PCF 326 and the SMF324. The system 300 or CN 320, or both, may also include a N24 referencepoint between the PCF 326 (in the home network) and a PCF 326 in avisited network. Additionally, the PCF 326 may exhibit a Npcfservice-based interface.

The UDM 327 may handle subscription-related information to support thenetwork entities' handling of communication sessions, and may storesubscription data of UE 301. For example, subscription data may becommunicated between the UDM 327 and the AMF 321 using a N8 referencepoint between the UDM 327 and the AMF. The UDM 327 can include twoparts, an application front end and a UDR (the front end and UDR are notshown in FIG. 3). The UDR may store subscription data and policy datafor the UDM 327 and the PCF 326, or structured data for exposure andapplication data (including PFDs for application detection, applicationrequest information for multiple UEs 301) for the NEF 323, or both. TheNudr service-based interface may be exhibited by the UDR 221 to allowthe UDM 327, PCF 326, and NEF 323 to access a particular set of thestored data, as well as to read, update (e.g., add, modify), delete, andsubscribe to notification of relevant data changes in the UDR. The UDMcan include a UDM front end, which is in charge of processingcredentials, location management, subscription management and so on.Several different front ends may serve the same user in differenttransactions. The UDM front end accesses subscription information storedin the UDR and performs authentication credential processing, useridentification handling, access authorization, registration/mobilitymanagement, and subscription management. The UDR may interact with theSMF 324 using a N10 reference point between the UDM 327 and the SMF 324.UDM 327 may also support SMS management, in which an SMS front endimplements the similar application logic as discussed previously.Additionally, the UDM 327 may exhibit the Nudm service-based interface.

The AF 328 may provide application influence on traffic routing, provideaccess to the network capability exposure (NCE), and interact with thepolicy framework for policy control. The NCE may be a mechanism thatallows the 5GC 320 and AF 328 to provide information to each other usingNEF 323, which may be used for edge computing implementations. In suchimplementations, the network operator and third party services may behosted close to the UE 301 access point of attachment to achieve anefficient service delivery through the reduced end-to-end latency andload on the transport network. For edge computing implementations, the5GC may select a UPF 302 close to the UE 301 and execute trafficsteering from the UPF 302 to DN 303 using the N6 interface. This may bebased on the UE subscription data, UE location, and information providedby the AF 328. In this way, the AF 328 may influence UPF (re)selectionand traffic routing. Based on operator deployment, when AF 328 isconsidered to be a trusted entity, the network operator may permit AF328 to interact directly with relevant NFs. Additionally, the AF 328 mayexhibit a Naf service-based interface.

The NSSF 329 may select a set of network slice instances serving the UE301. The NSSF 329 may also determine allowed NSSAI and the mapping tothe subscribed single network slice selection assistance information(S-NSSAI), if needed. The NSSF 329 may also determine the AMF set to beused to serve the UE 301, or a list of candidate AMF(s) 321 based on asuitable configuration and possibly by querying the NRF 325. Theselection of a set of network slice instances for the UE 301 may betriggered by the AMF 321 with which the UE 301 is registered byinteracting with the NSSF 329, which may lead to a change of AMF 321.The NSSF 329 may interact with the AMF 321 using an N22 reference pointbetween AMF 321 and NSSF 329; and may communicate with another NSSF 329in a visited network using a N31 reference point (not shown by FIG. 3).Additionally, the NSSF 329 may exhibit a Nnssf service-based interface.

As discussed previously, the CN 320 can include an SMSF, which may beresponsible for SMS subscription checking and verification, and relayingSM messages to or from the UE 301 to or from other entities, such as anSMS-GMSC/IWMSC/SMS-router. The SMS may also interact with AMF 321 andUDM 327 for a notification procedure that the UE 301 is available forSMS transfer (e.g., set a UE not reachable flag, and notifying UDM 327when UE 301 is available for SMS).

The CN 120 may also include other elements that are not shown in FIG. 3,such as a data storage system, a 5G-EIR, a security edge protectionpro10 (SEPP), and the like. The data storage system can include astructured data storage function (SDSF), an unstructured data storagefunction (UDSF), or both, among others. Any network function may storeand retrieve unstructured data to or from the UDSF (e.g., UE contexts),using a N18 reference point between any NF and the UDSF (not shown inFIG. 3). Individual network functions may share a UDSF for storing theirrespective unstructured data or individual network functions may eachhave their own UDSF located at or near the individual network functions.Additionally, the UDSF may exhibit a Nudsf service-based interface (notshown in FIG. 3). The 5G-EIR may be a network function that checks thestatus of permanent equipment identifiers (PEI) for determining whetherparticular equipment or entities are blacklisted from the network; andthe SEPP may be a non-transparent pro10 that performs topology hiding,message filtering, and policing on inter-PLMN control plane interfaces.

In some implementations, there may be additional or alternativereference points or service-based interfaces, or both, between thenetwork function services in the network functions. However, theseinterfaces and reference points have been omitted from FIG. 3 forclarity. In one example, the CN 320 can include a Nx interface, which isan inter-CN interface between the MME (e.g., MME 221) and the AMF 321 inorder to enable interworking between CN 320 and CN 220. Other exampleinterfaces or reference points can include a N5g-EIR service-basedinterface exhibited by a 5G-EIR, a N27 reference point between the NRFin the visited network and the NRF in the home network, or a N31reference point between the NSSF in the visited network and the NSSF inthe home network, among others.

In some implementations, the components of the CN 220 may be implementedin one physical node or separate physical nodes and can includecomponents to read and execute instructions from a machine-readable orcomputer-readable medium (e.g., a non-transitory machine-readablestorage medium). In some implementations, the components of CN 320 maybe implemented in a same or similar manner as discussed herein withregard to the components of CN 220. In some implementations, NFV isutilized to virtualize any or all of the above-described network nodefunctions using executable instructions stored in one or morecomputer-readable storage mediums, as described in further detail below.A logical instantiation of the CN 220 may be referred to as a networkslice, and individual logical instantiations of the CN 220 may providespecific network capabilities and network characteristics. A logicalinstantiation of a portion of the CN 220 may be referred to as a networksub-slice, which can include the P-GW 223 and the PCRF 226.

As used herein, the terms “instantiate,” “instantiation,” and the likemay refer to the creation of an instance, and an “instance” may refer toa concrete occurrence of an object, which may occur, for example, duringexecution of program code. A network instance may refer to informationidentifying a domain, which may be used for traffic detection androuting in case of different IP domains or overlapping IP addresses. Anetwork slice instance may refer to a set of network functions (NFs)instances and the resources (e.g., compute, storage, and networkingresources) required to deploy the network slice.

With respect to 5G systems (see, e.g., FIG. 3), a network slice caninclude a RAN part and a CN part. The support of network slicing relieson the principle that traffic for different slices is handled bydifferent PDU sessions. The network can realize the different networkslices by scheduling or by providing different L1/L2 configurations, orboth. The UE 301 provides assistance information for network sliceselection in an appropriate RRC message if it has been provided by NAS.In some implementations, while the network can support large number ofslices, the UE need not support more than 8 slices simultaneously.

A network slice can include the CN 320 control plane and user plane NFs,NG-RANs 310 in a serving PLMN, and a N3IWF functions in the servingPLMN. Individual network slices may have different S-NSSAI or differentSSTs, or both. NSSAI includes one or more S-NSSAIs, and each networkslice is uniquely identified by an S-NSSAI. Network slices may differfor supported features and network functions optimizations. In someimplementations, multiple network slice instances may deliver the sameservices or features but for different groups of UEs 301 (e.g.,enterprise users). For example, individual network slices may deliverdifferent committed service(s) or may be dedicated to a particularcustomer or enterprise, or both. In this example, each network slice mayhave different S-NSSAIs with the same SST but with different slicedifferentiators. Additionally, a single UE may be served with one ormore network slice instances simultaneously using a 5G AN, and the UEmay be associated with eight different S-NSSAIs. Moreover, an AMF 321instance serving an individual UE 301 may belong to each of the networkslice instances serving that UE.

Network slicing in the NG-RAN 310 involves RAN slice awareness. RANslice awareness includes differentiated handling of traffic fordifferent network slices, which have been pre-configured. Sliceawareness in the NG-RAN 310 is introduced at the PDU session level byindicating the S-NSSAI corresponding to a PDU session in all signalingthat includes PDU session resource information. How the NG-RAN 310supports the slice enabling in terms of NG-RAN functions (e.g., the setof network functions that comprise each slice) is implementationdependent. The NG-RAN 310 selects the RAN part of the network sliceusing assistance information provided by the UE 301 or the 5GC 320,which unambiguously identifies one or more of the pre-configured networkslices in the PLMN. The NG-RAN 310 also supports resource management andpolicy enforcement between slices as per SLAs. A single NG-RAN node maysupport multiple slices, and the NG-RAN 310 may also apply anappropriate RRM policy for the SLA in place to each supported slice. TheNG-RAN 310 may also support QoS differentiation within a slice.

The NG-RAN 310 may also use the UE assistance information for theselection of an AMF 321 during an initial attach, if available. TheNG-RAN 310 uses the assistance information for routing the initial NASto an AMF 321. If the NG-RAN 310 is unable to select an AMF 321 usingthe assistance information, or the UE 301 does not provide any suchinformation, the NG-RAN 310 sends the NAS signaling to a default AMF321, which may be among a pool of AMFs 321. For subsequent accesses, theUE 301 provides a temp ID, which is assigned to the UE 301 by the 5GC320, to enable the NG-RAN 310 to route the NAS message to theappropriate AMF 321 as long as the temp ID is valid. The NG-RAN 310 isaware of, and can reach, the AMF 321 that is associated with the tempID. Otherwise, the method for initial attach applies.

The NG-RAN 310 supports resource isolation between slices. NG-RAN 310resource isolation may be achieved by means of RRM policies andprotection mechanisms that should avoid that shortage of sharedresources if one slice breaks the service level agreement for anotherslice. In some implementations, it is possible to fully dedicate NG-RAN310 resources to a certain slice. How NG-RAN 310 supports resourceisolation is implementation dependent.

Some slices may be available only in part of the network. Awareness inthe NG-RAN 310 of the slices supported in the cells of its neighbors maybe beneficial for inter-frequency mobility in connected mode. The sliceavailability may not change within the UE's registration area. TheNG-RAN 310 and the 5GC 320 are responsible to handle a service requestfor a slice that may or may not be available in a given area. Admissionor rejection of access to a slice may depend on factors such as supportfor the slice, availability of resources, support of the requestedservice by NG-RAN 310.

The UE 301 may be associated with multiple network slicessimultaneously. In case the UE 301 is associated with multiple slicessimultaneously, only one signaling connection is maintained, and forintra-frequency cell reselection, the UE 301 tries to camp on the bestcell. For inter-frequency cell reselection, dedicated priorities can beused to control the frequency on which the UE 301 camps. The 5GC 320 isto validate that the UE 301 has the rights to access a network slice.Prior to receiving an Initial Context Setup Request message, the NG-RAN310 may be allowed to apply some provisional or local policies based onawareness of a particular slice that the UE 301 is requesting to access.During the initial context setup, the NG-RAN 310 is informed of theslice for which resources are being requested.

FIG. 4 illustrates an example of infrastructure equipment 400. Theinfrastructure equipment 400 (or “system 400”) may be implemented as abase station, a radio head, a RAN node, such as the RAN nodes 111 or AP106 shown and described previously, an application server 130, or anyother component or device described herein. In other examples, thesystem 400 can be implemented in or by a UE.

The system 400 includes application circuitry 405, baseband circuitry410, one or more radio front end modules (RFEMs) 415, memory circuitry420, power management integrated circuitry (PMIC) 425, power teecircuitry 430, network controller circuitry 435, network interfaceconnector 440, satellite positioning circuitry 445, and user interfacecircuitry 450. In some implementations, the system 400 can includeadditional elements such as, for example, memory, storage, a display, acamera, one or more sensors, or an input/output (I/O) interface, orcombinations of them, among others. In other examples, the componentsdescribed with reference to the system 400 may be included in more thanone device. For example, the various circuitries may be separatelyincluded in more than one device for CRAN, vBBU, or otherimplementations.

The application circuitry 405 includes circuitry such as, but notlimited to, one or more processors (or processor cores), cache memory,one or more of low drop-out voltage regulators (LDOs), interruptcontrollers, serial interfaces such as SPI, I2C or universalprogrammable serial interface module, real time clock (RTC),timer-counters including interval and watchdog timers, general purposeinput/output (I/O or IO), memory card controllers such as Secure Digital(SD) MultiMediaCard (MMC) or similar, Universal Serial Bus (USB)interfaces, Mobile Industry Processor Interface (MIPI) interfaces andJoint Test Access Group (JTAG) test access ports. The processors (orcores) of the application circuitry 405 may be coupled with or caninclude memory or storage elements and may be configured to executeinstructions stored in the memory or storage to enable variousapplications or operating systems to run on the system 400. In someimplementations, the memory or storage elements can include on-chipmemory circuitry, which can include any suitable volatile ornon-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, Flash memory,solid-state memory, or combinations of them, among other types ofmemory.

The processor(s) of the application circuitry 405 can include, forexample, one or more processor cores (CPUs), one or more applicationprocessors, one or more graphics processing units (GPUs), one or morereduced instruction set computing (RISC) processors, one or more AcornRISC Machine (ARM) processors, one or more complex instruction setcomputing (CISC) processors, one or more digital signal processors(DSP), one or more FPGAs, one or more PLDs, one or more ASICs, one ormore microprocessors or controllers, or combinations of them, amongothers. In some implementations, the application circuitry 405 caninclude, or may be, a special-purpose processor or controller configuredto carry out the various techniques described here. As examples, theprocessor(s) of application circuitry 405 can include one or more IntelPentium®, Core®, or Xeon® processor(s); Advanced Micro Devices (AMD)Ryzen® processor(s), Accelerated Processing Units (APUs), or Epyc®processors; ARM-based processor(s) licensed from ARM Holdings, Ltd. suchas the ARM Cortex-A family of processors and the ThunderX2® provided byCavium™, Inc.; a MIPS-based design from MIPS Technologies, Inc. such asMIPS Warrior P-class processors; and/or the like. In someimplementations, the system 400 may not utilize application circuitry405, and instead can include a special-purpose processor or controllerto process IP data received from an EPC or 5GC, for example.

In some implementations, the application circuitry 405 can include oneor more hardware accelerators, which may be microprocessors,programmable processing devices, or the like. The one or more hardwareaccelerators can include, for example, computer vision (CV) or deeplearning (DL) accelerators, or both. In some implementations, theprogrammable processing devices may be one or more a field-programmabledevices (FPDs) such as field-programmable gate arrays (FPGAs) and thelike; programmable logic devices (PLDs) such as complex PLDs (CPLDs) orhigh-capacity PLDs (HCPLDs); ASICs such as structured ASICs;programmable SoCs (PSoCs), or combinations of them, among others. Insuch implementations, the circuitry of application circuitry 405 caninclude logic blocks or logic fabric, and other interconnected resourcesthat may be programmed to perform various functions, such as theprocedures, methods, functions described herein. In someimplementations, the circuitry of application circuitry 405 can includememory cells (e.g., erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), flashmemory, static memory (e.g., static random access memory (SRAM) oranti-fuses)) used to store logic blocks, logic fabric, data, or otherdata in look-up-tables (LUTs) and the like.

The baseband circuitry 410 may be implemented, for example, as asolder-down substrate including one or more integrated circuits, asingle packaged integrated circuit soldered to a main circuit board or amulti-chip module containing two or more integrated circuits.

The user interface circuitry 450 can include one or more user interfacesdesigned to enable user interaction with the system 400 or peripheralcomponent interfaces designed to enable peripheral component interactionwith the system 400. User interfaces can include, but are not limitedto, one or more physical or virtual buttons (e.g., a reset button), oneor more indicators (e.g., light emitting diodes (LEDs)), a physicalkeyboard or keypad, a mouse, a touchpad, a touchscreen, speakers orother audio emitting devices, microphones, a printer, a scanner, aheadset, a display screen or display device, or combinations of them,among others. Peripheral component interfaces can include, but are notlimited to, a nonvolatile memory port, a universal serial bus (USB)port, an audio jack, a power supply interface, among others.

The radio front end modules (RFEMs) 415 can include a millimeter wave(mmWave) RFEM and one or more sub-mmWave radio frequency integratedcircuits (RFICs). In some implementations, the one or more sub-mmWaveRFICs may be physically separated from the mmWave RFEM. The RFICs caninclude connections to one or more antennas or antenna arrays (see,e.g., antenna array 611 of FIG. 6), and the RFEM may be connected tomultiple antennas. In some implementations, both mmWave and sub-mmWaveradio functions may be implemented in the same physical RFEM 415, whichincorporates both mmWave antennas and sub-mmWave.

The memory circuitry 420 can include one or more of volatile memory,such as dynamic random access memory (DRAM) or synchronous dynamicrandom access memory (SDRAM), and nonvolatile memory (NVM), such ashigh-speed electrically erasable memory (commonly referred to as Flashmemory), phase change random access memory (PRAM), or magnetoresistiverandom access memory (MRAM), or combinations of them, among others. Insome implementations, the memory circuitry 420 can includethree-dimensional (3D) cross-point (XPOINT) memories from Intel® andMicron®. Memory circuitry 420 may be implemented as one or more ofsolder down packaged integrated circuits, socketed memory modules andplug-in memory cards, for example.

The PMIC 425 can include voltage regulators, surge protectors, poweralarm detection circuitry, and one or more backup power sources such asa battery or capacitor. The power alarm detection circuitry may detectone or more of brown out (under-voltage) and surge (over-voltage)conditions. The power tee circuitry 430 may provide for electrical powerdrawn from a network cable to provide both power supply and dataconnectivity to the infrastructure equipment 400 using a single cable.

The network controller circuitry 435 may provide connectivity to anetwork using a standard network interface protocol such as Ethernet,Ethernet over GRE Tunnels, Ethernet over Multiprotocol Label Switching(MPLS), or some other suitable protocol. Network connectivity may beprovided to and from the infrastructure equipment 400 using networkinterface connector 440 using a physical connection, which may beelectrical (commonly referred to as a “copper interconnect”), optical,or wireless. The network controller circuitry 435 can include one ormore dedicated processors or FPGAs, or both, to communicate using one ormore of the aforementioned protocols. In some implementations, thenetwork controller circuitry 435 can include multiple controllers toprovide connectivity to other networks using the same or differentprotocols.

The positioning circuitry 445 includes circuitry to receive and decodesignals transmitted or broadcasted by a positioning network of a globalnavigation satellite system (GNSS). Examples of a GNSS include UnitedStates' Global Positioning System (GPS), Russia's Global NavigationSystem (GLONASS), the European Union's Galileo system, China's BeiDouNavigation Satellite System, a regional navigation system or GNSSaugmentation system (e.g., Navigation with Indian Constellation (NAVIC),Japan's Quasi-Zenith Satellite System (QZSS), France's DopplerOrbitography and Radio-positioning Integrated by Satellite (DORIS)),among other systems. The positioning circuitry 445 can include varioushardware elements (e.g., including hardware devices such as switches,filters, amplifiers, antenna elements, and the like to facilitate OTAcommunications) to communicate with components of a positioning network,such as navigation satellite constellation nodes. In someimplementations, the positioning circuitry 445 can include aMicro-Technology for Positioning, Navigation, and Timing (Micro-PNT) ICthat uses a master timing clock to perform position tracking andestimation without GNSS assistance. The positioning circuitry 445 mayalso be part of, or interact with, the baseband circuitry 410 or RFEMs415, or both, to communicate with the nodes and components of thepositioning network. The positioning circuitry 445 may also provide data(e.g., position data, time data) to the application circuitry 405, whichmay use the data to synchronize operations with various infrastructure(e.g., RAN nodes 111).

The components shown by FIG. 4 may communicate with one another usinginterface circuitry, which can include any number of bus or interconnect(IX) technologies such as industry standard architecture (ISA), extendedISA (EISA), peripheral component interconnect (PCI), peripheralcomponent interconnect extended (PCIx), PCI express (PCIe), or anynumber of other technologies. The bus or IX may be a proprietary bus,for example, used in a SoC based system. Other bus or IX systems may beincluded, such as an I2C interface, an SPI interface, point to pointinterfaces, and a power bus, among others.

FIG. 5 illustrates an example of a platform 500 (or “device 500”). Insome implementations, the computer platform 500 may be suitable for useas UEs 101, 201, 301, application servers 130, or any other component ordevice discussed herein. The platform 500 can include any combinationsof the components shown in the example. The components of platform 500(or portions thereof) may be implemented as integrated circuits (ICs),discrete electronic devices, or other modules, logic, hardware,software, firmware, or a combination of them adapted in the computerplatform 500, or as components otherwise incorporated within a chassisof a larger system. The block diagram of FIG. 5 is intended to show ahigh level view of components of the platform 500. However, in someimplementations, the platform 500 can include fewer, additional, oralternative components, or a different arrangement of the componentsshown in FIG. 5.

The application circuitry 505 includes circuitry such as, but notlimited to, one or more processors (or processor cores), cache memory,and one or more of LDOs, interrupt controllers, serial interfaces suchas SPI, I2C or universal programmable serial interface module, RTC,timer-counters including interval and watchdog timers, general purposeI/O, memory card controllers such as SD MMC or similar, USB interfaces,MIPI interfaces, and JTAG test access ports. The processors (or cores)of the application circuitry 505 may be coupled with or can includememory/storage elements and may be configured to execute instructionsstored in the memory or storage to enable various applications oroperating systems to run on the system 500. In some implementations, thememory or storage elements may be on-chip memory circuitry, which caninclude any suitable volatile or non-volatile memory, such as DRAM,SRAM, EPROM, EEPROM, Flash memory, solid-state memory, or combinationsof them, among other types of memory.

The processor(s) of application circuitry 405 can include, for example,one or more processor cores, one or more application processors, one ormore GPUs, one or more RISC processors, one or more ARM processors, oneor more CISC processors, one or more DSP, one or more FPGAs, one or morePLDs, one or more ASICs, one or more microprocessors or controllers, amultithreaded processor, an ultra-low voltage processor, an embeddedprocessor, some other known processing element, or any suitablecombination thereof. In some implementations, the application circuitry405 can include, or may be, a special-purpose processor/controller tocarry out the techniques described herein.

As examples, the processor(s) of application circuitry 505 can includean Intel® Architecture Core™ based processor, such as a Quark™, anAtom™, an i3, an i5, an i7, or an MCU-class processor, or another suchprocessor available from Intel® Corporation, Santa Clara, Calif. Theprocessors of the application circuitry 505 may also be one or more ofAdvanced Micro Devices (AMD) Ryzen® processor(s) or AcceleratedProcessing Units (APUs); A5-A9 processor(s) from Apple® Inc.,Snapdragon™ processor(s) from Qualcomm® Technologies, Inc., TexasInstruments, Inc.® Open Multimedia Applications Platform (OMAP)™processor(s); a MIPS-based design from MIPS Technologies, Inc. such asMIPS Warrior M-class, Warrior I-class, and Warrior P-class processors;an ARM-based design licensed from ARM Holdings, Ltd., such as the ARMCortex-A, Cortex-R, and Cortex-M family of processors; or the like. Insome implementations, the application circuitry 505 may be a part of asystem on a chip (SoC) in which the application circuitry 505 and othercomponents are formed into a single integrated circuit, or a singlepackage, such as the Edison™ or Galileo™ SoC boards from Intel®Corporation.

Additionally or alternatively, the application circuitry 505 can includecircuitry such as, but not limited to, one or more a field-programmabledevices (FPDs) such as FPGAs; programmable logic devices (PLDs) such ascomplex PLDs (CPLDs), high-capacity PLDs (HCPLDs); ASICs such asstructured ASICs; programmable SoCs (PSoCs), or combinations of them,among others. In some implementations, the application circuitry 505 caninclude logic blocks or logic fabric, and other interconnected resourcesthat may be programmed to perform various functions, such as theprocedures, methods, functions described herein. In someimplementations, the application circuitry 505 can include memory cells(e.g., erasable programmable read-only memory (EPROM), electricallyerasable programmable read-only memory (EEPROM), flash memory, staticmemory (e.g., static random access memory (SRAM), or anti-fuses)) usedto store logic blocks, logic fabric, data, or other data in look-uptables (LUTs) and the like.

The baseband circuitry 510 may be implemented, for example, as asolder-down substrate including one or more integrated circuits, asingle packaged integrated circuit soldered to a main circuit board or amulti-chip module containing two or more integrated circuits. Thevarious hardware electronic elements of baseband circuitry 510 arediscussed with regard to FIG. 6.

The RFEMs 515 may comprise a millimeter wave (mmWave) RFEM and one ormore sub-mmWave radio frequency integrated circuits (RFICs). In someimplementations, the one or more sub-mmWave RFICs may be physicallyseparated from the mmWave RFEM. The RFICs can include connections to oneor more antennas or antenna arrays (see, e.g., antenna array 611 of FIG.6), and the RFEM may be connected to multiple antennas. In someimplementations, both mmWave and sub-mmWave radio functions may beimplemented in the same physical RFEM 515, which incorporates bothmmWave antennas and sub-mmWave.

The memory circuitry 520 can include any number and type of memorydevices used to provide for a given amount of system memory. Asexamples, the memory circuitry 520 can include one or more of volatilememory, such as random access memory (RAM), dynamic RAM (DRAM) orsynchronous dynamic RAM (SDRAM), and nonvolatile memory (NVM), such ashigh-speed electrically erasable memory (commonly referred to as Flashmemory), phase change random access memory (PRAM), or magnetoresistiverandom access memory (MRAM), or combinations of them, among others. Thememory circuitry 520 may be developed in accordance with a JointElectron Devices Engineering Council (JEDEC) low power double data rate(LPDDR)-based design, such as LPDDR2, LPDDR3, LPDDR4, or the like.Memory circuitry 520 may be implemented as one or more of solder downpackaged integrated circuits, single die package (SDP), dual die package(DDP) or quad die package (Q17P), socketed memory modules, dual inlinememory modules (DIMMs) including microDIMMs or MiniDIMMs, or solderedonto a motherboard using a ball grid array (BGA). In low powerimplementations, the memory circuitry 520 may be on-die memory orregisters associated with the application circuitry 505. To provide forpersistent storage of information such as data, applications, operatingsystems and so forth, memory circuitry 520 can include one or more massstorage devices, which can include, for example, a solid state diskdrive (SSDD), hard disk drive (HDD), a micro HDD, resistance changememories, phase change memories, holographic memories, or chemicalmemories, among others. In some implementations, the computer platform500 may incorporate the three-dimensional (3D) cross-point (XPOINT)memories from Intel® and Micron®.

The removable memory circuitry 523 can include devices, circuitry,enclosures, housings, ports or receptacles, among others, used to coupleportable data storage devices with the platform 500. These portable datastorage devices may be used for mass storage purposes, and can include,for example, flash memory cards (e.g., Secure Digital (SD) cards,microSD cards, xD picture cards), and USB flash drives, optical discs,or external HDDs, or combinations of them, among others.

The platform 500 may also include interface circuitry (not shown) forconnecting external devices with the platform 500. The external devicesconnected to the platform 500 using the interface circuitry includesensor circuitry 521 and electro-mechanical components (EMCs) 522, aswell as removable memory devices coupled to removable memory circuitry523.

The sensor circuitry 521 include devices, modules, or subsystems whosepurpose is to detect events or changes in its environment and send theinformation (e.g., sensor data) about the detected events to one or moreother devices, modules, or subsystems. Examples of such sensors includeinertial measurement units (IMUs) such as accelerometers, gyroscopes, ormagnetometers; microelectromechanical systems (MEMS) ornanoelectromechanical systems (NEMS) including 3-axis accelerometers,3-axis gyroscopes, or magnetometers; level sensors; flow sensors;temperature sensors (e.g., thermistors); pressure sensors; barometricpressure sensors; gravimeters; altimeters; image capture devices (e.g.,cameras or lensless apertures); light detection and ranging (LiDAR)sensors; proximity sensors (e.g., infrared radiation detector and thelike), depth sensors, ambient light sensors, ultrasonic transceivers;microphones or other audio capture devices, or combinations of them,among others.

The EMCs 522 include devices, modules, or subsystems whose purpose is toenable the platform 500 to change its state, position, or orientation,or move or control a mechanism, system, or subsystem. Additionally, theEMCs 522 may be configured to generate and send messages or signaling toother components of the platform 500 to indicate a current state of theEMCs 522. Examples of the EMCs 522 include one or more power switches,relays, such as electromechanical relays (EMRs) or solid state relays(SSRs), actuators (e.g., valve actuators), an audible sound generator, avisual warning device, motors (e.g., DC motors or stepper motors),wheels, thrusters, propellers, claws, clamps, hooks, or combinations ofthem, among other electro-mechanical components. In someimplementations, the platform 500 is configured to operate one or moreEMCs 522 based on one or more captured events, instructions, or controlsignals received from a service provider or clients, or both.

In some implementations, the interface circuitry may connect theplatform 500 with positioning circuitry 545. The positioning circuitry545 includes circuitry to receive and decode signals transmitted orbroadcasted by a positioning network of a GNSS. Examples of a GNSSinclude United States' GPS, Russia's GLONASS, the European Union'sGalileo system, China's BeiDou Navigation Satellite System, a regionalnavigation system or GNSS augmentation system (e.g., NAVIC), Japan'sQZSS, France's DORIS, among other systems. The positioning circuitry 545comprises various hardware elements (e.g., including hardware devicessuch as switches, filters, amplifiers, antenna elements, and the like tofacilitate OTA communications) to communicate with components of apositioning network, such as navigation satellite constellation nodes.In some implementations, the positioning circuitry 545 can include aMicro-PNT IC that uses a master timing clock to perform positiontracking or estimation without GNSS assistance. The positioningcircuitry 545 may also be part of, or interact with, the basebandcircuitry 410 or RFEMs 515, or both, to communicate with the nodes andcomponents of the positioning network. The positioning circuitry 545 mayalso provide data (e.g., position data, time data) to the applicationcircuitry 505, which may use the data to synchronize operations withvarious infrastructure (e.g., radio base stations), for turn-by-turnnavigation applications, or the like.

In some implementations, the interface circuitry may connect theplatform 500 with Near-Field Communication (NFC) circuitry 540. The NFCcircuitry 540 is configured to provide contactless, short-rangecommunications based on radio frequency identification (RFID) standards,in which magnetic field induction is used to enable communicationbetween NFC circuitry 540 and NFC-enabled devices external to theplatform 500 (e.g., an “NFC touchpoint”). The NFC circuitry 540 includesan NFC controller coupled with an antenna element and a processorcoupled with the NFC controller. The NFC controller may be a chip or ICproviding NFC functionalities to the NFC circuitry 540 by executing NFCcontroller firmware and an NFC stack. The NFC stack may be executed bythe processor to control the NFC controller, and the NFC controllerfirmware may be executed by the NFC controller to control the antennaelement to emit short-range RF signals. The RF signals may power apassive NFC tag (e.g., a microchip embedded in a sticker or wristband)to transmit stored data to the NFC circuitry 540, or initiate datatransfer between the NFC circuitry 540 and another active NFC device(e.g., a smartphone or an NFC-enabled POS terminal) that is proximate tothe platform 500.

The driver circuitry 546 can include software and hardware elements thatoperate to control particular devices that are embedded in the platform500, attached to the platform 500, or otherwise communicatively coupledwith the platform 500. The driver circuitry 546 can include individualdrivers allowing other components of the platform 500 to interact withor control various input/output (I/O) devices that may be presentwithin, or connected to, the platform 500. For example, the drivercircuitry 546 can include a display driver to control and allow accessto a display device, a touchscreen driver to control and allow access toa touchscreen interface of the platform 500, sensor drivers to obtainsensor readings of sensor circuitry 521 and control and allow access tosensor circuitry 521, EMC drivers to obtain actuator positions of theEMCs 522 or control and allow access to the EMCs 522, a camera driver tocontrol and allow access to an embedded image capture device, audiodrivers to control and allow access to one or more audio devices.

The power management integrated circuitry (PMIC) 525 (also referred toas “power management circuitry 525”) may manage power provided tovarious components of the platform 500. In particular, with respect tothe baseband circuitry 510, the PMIC 525 may control power-sourceselection, voltage scaling, battery charging, or DC-to-DC conversion.The PMIC 525 may be included when the platform 500 is capable of beingpowered by a battery 530, for example, when the device is included in aUE 101, 201, 301.

In some implementations, the PMIC 525 may control, or otherwise be partof, various power saving mechanisms of the platform 500. For example, ifthe platform 500 is in an RRC_Connected state, where it is stillconnected to the RAN node as it expects to receive traffic shortly, thenit may enter a state known as Discontinuous Reception Mode (DRX) after aperiod of inactivity. During this state, the platform 500 may power downfor brief intervals of time and thus save power. If there is no datatraffic activity for an extended period of time, then the platform 500may transition off to an RRC_Idle state, where it disconnects from thenetwork and does not perform operations such as channel quality feedbackor handover. This can allow the platform 500 to enter a very low powerstate, where it periodically wakes up to listen to the network and thenpowers down again. In some implementations, the platform 500 may notreceive data in the RRC_Idle state and instead must transition back toRRC_Connected state to receive data. An additional power saving mode mayallow a device to be unavailable to the network for periods longer thana paging interval (ranging from seconds to a few hours). During thistime, the device may be unreachable to the network and may power downcompletely. Any data sent during this time may incurs a large delay andit is assumed the delay is acceptable.

A battery 530 may power the platform 500, although In someimplementations the platform 500 may be deployed in a fixed location,and may have a power supply coupled to an electrical grid. The battery530 may be a lithium ion battery, a metal-air battery, such as azinc-air battery, an aluminum-air battery, or a lithium-air battery,among others. In some implementations, such as in V2X applications, thebattery 530 may be a typical lead-acid automotive battery.

In some implementations, the battery 530 may be a “smart battery,” whichincludes or is coupled with a Battery Management System (BMS) or batterymonitoring integrated circuitry. The BMS may be included in the platform500 to track the state of charge (SoCh) of the battery 530. The BMS maybe used to monitor other parameters of the battery 530 to providefailure predictions, such as the state of health (SoH) and the state offunction (SoF) of the battery 530. The BMS may communicate theinformation of the battery 530 to the application circuitry 505 or othercomponents of the platform 500. The BMS may also include ananalog-to-digital (ADC) convertor that allows the application circuitry505 to directly monitor the voltage of the battery 530 or the currentflow from the battery 530. The battery parameters may be used todetermine actions that the platform 500 may perform, such astransmission frequency, network operation, or sensing frequency, amongothers.

A power block, or other power supply coupled to an electrical grid maybe coupled with the BMS to charge the battery 530. In someimplementations, the power block 530 may be replaced with a wirelesspower receiver to obtain the power wirelessly, for example, through aloop antenna in the computer platform 500. In these examples, a wirelessbattery charging circuit may be included in the BMS. The specificcharging circuits chosen may depend on the size of the battery 530, andthus, the current required. The charging may be performed using theAirfuel standard promulgated by the Airfuel Alliance, the Qi wirelesscharging standard promulgated by the Wireless Power Consortium, or theRezence charging standard promulgated by the Alliance for WirelessPower, among others.

The user interface circuitry 550 includes various input/output (I/O)devices present within, or connected to, the platform 500, and includesone or more user interfaces designed to enable user interaction with theplatform 500 or peripheral component interfaces designed to enableperipheral component interaction with the platform 500. The userinterface circuitry 550 includes input device circuitry and outputdevice circuitry. Input device circuitry includes any physical orvirtual means for accepting an input including one or more physical orvirtual buttons (e.g., a reset button), a physical keyboard, keypad,mouse, touchpad, touchscreen, microphones, scanner, or headset, orcombinations of them, among others. The output device circuitry includesany physical or virtual means for showing information or otherwiseconveying information, such as sensor readings, actuator position(s), orother information. Output device circuitry can include any number orcombinations of audio or visual display, including one or more simplevisual outputs or indicators (e.g., binary status indicators (e.g.,light emitting diodes (LEDs)), multi-character visual outputs, or morecomplex outputs such as display devices or touchscreens (e.g., LiquidChrystal Displays (LCD), LED displays, quantum dot displays, orprojectors), with the output of characters, graphics, or multimediaobjects being generated or produced from the operation of the platform500. The output device circuitry may also include speakers or otheraudio emitting devices, or printer(s). In some implementations, thesensor circuitry 521 may be used as the input device circuitry (e.g., animage capture device or motion capture device), and one or more EMCs maybe used as the output device circuitry (e.g., an actuator to providehaptic feedback). In another example, NFC circuitry comprising an NFCcontroller coupled with an antenna element and a processing device maybe included to read electronic tags or connect with another NFC-enableddevice. Peripheral component interfaces can include, but are not limitedto, a non-volatile memory port, a USB port, an audio jack, or a powersupply interface.

Although not shown, the components of platform 500 may communicate withone another using a suitable bus or interconnect (IX) technology, whichcan include any number of technologies, including ISA, EISA, PCI, PCIx,PCIe, a Time-Trigger Protocol (TTP) system, a FlexRay system, or anynumber of other technologies. The bus or IX may be a proprietary bus orIX, for example, used in a SoC based system. Other bus or IX systems maybe included, such as an I2C interface, an SPI interface, point-to-pointinterfaces, and a power bus, among others.

FIG. 6 illustrates example components of baseband circuitry 610 andradio front end modules (RFEM) 615. The baseband circuitry 610 cancorrespond to the baseband circuitry 410 and 510 of FIGS. 4 and 5,respectively. The RFEM 615 can correspond to the RFEM 415 and 515 ofFIGS. 4 and 5, respectively. As shown, the RFEMs 615 can include RadioFrequency (RF) circuitry 606, front-end module (FEM) circuitry 608, andantenna array 611 coupled together.

The baseband circuitry 610 includes circuitry configured to carry outvarious radio or network protocol and control functions that enablecommunication with one or more radio networks using the RF circuitry606. The radio control functions can include, but are not limited to,signal modulation and demodulation, encoding and decoding, and radiofrequency shifting. In some implementations, modulation and demodulationcircuitry of the baseband circuitry 610 can include Fast-FourierTransform (FFT), precoding, or constellation mapping and demappingfunctionality. In some implementations, encoding and decoding circuitryof the baseband circuitry 610 can include convolution, tail-bitingconvolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoderand decoder functionality. Modulation and demodulation and encoder anddecoder functionality are not limited to these examples and can includeother suitable functionality in other examples. The baseband circuitry610 is configured to process baseband signals received from a receivesignal path of the RF circuitry 606 and to generate baseband signals fora transmit signal path of the RF circuitry 606. The baseband circuitry610 is configured to interface with application circuitry (e.g., theapplication circuitry 405, 505 shown in FIGS. 4 and 5) for generationand processing of the baseband signals and for controlling operations ofthe RF circuitry 606. The baseband circuitry 610 may handle variousradio control functions.

The aforementioned circuitry and control logic of the baseband circuitry610 can include one or more single or multi-core processors. Forexample, the one or more processors can include a 3G baseband processor604A, a 4G or LTE baseband processor 604B, a 5G or NR baseband processor604C, or some other baseband processor(s) 604D for other existinggenerations, generations in development or to be developed in the future(e.g., sixth generation (6G)). In some implementations, some or all ofthe functionality of baseband processors 604A-D may be included inmodules stored in the memory 604G and executed using one or moreprocessors such as a Central Processing Unit (CPU) 604E. In someimplementations, some or all of the functionality of baseband processors604A-D may be provided as hardware accelerators (e.g., FPGAs or ASICs)loaded with the appropriate bit streams or logic blocks stored inrespective memory cells. In some implementations, the memory 604G maystore program code of a real-time OS (RTOS) which, when executed by theCPU 604E (or other processor), is to cause the CPU 604E (or otherprocessor) to manage resources of the baseband circuitry 610, scheduletasks, or carry out other operations. Examples of the RTOS can includeOperating System Embedded (OSE)™ provided by Enea®, Nucleus RTOS™provided by Mentor Graphics®, Versatile Real-Time Executive (VRTX)provided by Mentor Graphics®, ThreadX™ provided by Express Logic®,FreeRTOS, REX OS provided by Qualcomm®, OKL4 provided by Open Kernel(OK) Labs®, or any other suitable RTOS, such as those discussed herein.In some implementations, the baseband circuitry 610 includes one or moreaudio digital signal processors (DSP) 604F. An audio DSP 604F caninclude elements for compression and decompression and echo cancellationand can include other suitable processing elements.

In some implementations, each of the processors 604A-604E includerespective memory interfaces to send and receive data to and from thememory 604G. The baseband circuitry 610 may further include one or moreinterfaces to communicatively couple to other circuitries or devices,such as an interface to send and receive data to and from memoryexternal to the baseband circuitry 610; an application circuitryinterface to send and receive data to and from the application circuitry405, 505 of FIG. 4 and XT); an RF circuitry interface to send andreceive data to and from RF circuitry 606 of FIG. 6; a wireless hardwareconnectivity interface to send and receive data to and from one or morewireless hardware elements (e.g., Near Field Communication (NFC)components, Bluetooth®/Bluetooth® Low Energy components, Wi-Fi®components, and/or the like); and a power management interface to sendand receive power or control signals to and from the PMIC 525.

In some implementations (which may be combined with the above describedexamples), the baseband circuitry 610 includes one or more digitalbaseband systems, which are coupled with one another using aninterconnect subsystem and to a CPU subsystem, an audio subsystem, andan interface subsystem. The digital baseband subsystems may also becoupled to a digital baseband interface and a mixed-signal basebandsubsystem using another interconnect subsystem. Each of the interconnectsubsystems can include a bus system, point-to-point connections,network-on-chip (NOC) structures, or some other suitable bus orinterconnect technology, such as those discussed herein. The audiosubsystem can include DSP circuitry, buffer memory, program memory,speech processing accelerator circuitry, data converter circuitry suchas analog-to-digital and digital-to-analog converter circuitry, analogcircuitry including one or more of amplifiers and filters, among othercomponents. In some implementations, the baseband circuitry 610 caninclude protocol processing circuitry with one or more instances ofcontrol circuitry (not shown) to provide control functions for thedigital baseband circuitry or radio frequency circuitry (e.g., the radiofront end modules 615).

In some implementations, the baseband circuitry 610 includes individualprocessing device(s) to operate one or more wireless communicationprotocols (e.g., a “multi-protocol baseband processor” or “protocolprocessing circuitry”) and individual processing device(s) to implementPHY layer functions. In some implementations, the PHY layer functionsinclude the aforementioned radio control functions. In someimplementations, the protocol processing circuitry operates orimplements various protocol layers or entities of one or more wirelesscommunication protocols. For example, the protocol processing circuitrymay operate LTE protocol entities or 5G NR protocol entities, or both,when the baseband circuitry 610 or RF circuitry 606, or both, are partof mmWave communication circuitry or some other suitable cellularcommunication circuitry. In this example, the protocol processingcircuitry can operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. Insome implementations, the protocol processing circuitry may operate oneor more IEEE-based protocols when the baseband circuitry 610 or RFcircuitry 606, or both, are part of a Wi-Fi communication system. Inthis example, the protocol processing circuitry can operate Wi-Fi MACand logical link control (LLC) functions. The protocol processingcircuitry can include one or more memory structures (e.g., 604G) tostore program code and data for operating the protocol functions, aswell as one or more processing cores to execute the program code andperform various operations using the data. The baseband circuitry 610may also support radio communications for more than one wirelessprotocol.

The various hardware elements of the baseband circuitry 610 discussedherein may be implemented, for example, as a solder-down substrateincluding one or more integrated circuits (ICs), a single packaged ICsoldered to a main circuit board or a multi-chip module containing twoor more ICs. In some implementations, the components of the basebandcircuitry 610 may be suitably combined in a single chip or chipset, ordisposed on a same circuit board. In some implementations, some or allof the constituent components of the baseband circuitry 610 and RFcircuitry 606 may be implemented together such as, for example, a systemon a chip (SoC) or System-in-Package (SiP). In some implementations,some or all of the constituent components of the baseband circuitry 610may be implemented as a separate SoC that is communicatively coupledwith and RF circuitry 606 (or multiple instances of RF circuitry 606).In some implementations, some or all of the constituent components ofthe baseband circuitry 610 and the application circuitry 405, 505 may beimplemented together as individual SoCs mounted to a same circuit board(e.g., a “multi-chip package”).

In some implementations, the baseband circuitry 610 may provide forcommunication compatible with one or more radio technologies. Forexample, the baseband circuitry 610 may support communication with anE-UTRAN or other WMAN, a WLAN, or a WPAN. Examples in which the basebandcircuitry 610 is configured to support radio communications of more thanone wireless protocol may be referred to as multi-mode basebandcircuitry.

The RF circuitry 606 may enable communication with wireless networksusing modulated electromagnetic radiation through a non-solid medium. Insome implementations, the RF circuitry 606 can include switches,filters, or amplifiers, among other components, to facilitate thecommunication with the wireless network. The RF circuitry 606 caninclude a receive signal path, which can include circuitry todown-convert RF signals received from the FEM circuitry 608 and providebaseband signals to the baseband circuitry 610. The RF circuitry 606 mayalso include a transmit signal path, which can include circuitry toup-convert baseband signals provided by the baseband circuitry 610 andprovide RF output signals to the FEM circuitry 608 for transmission.

The receive signal path of the RF circuitry 606 includes mixer circuitry606 a, amplifier circuitry 606 b and filter circuitry 606 c. In someimplementations, the transmit signal path of the RF circuitry 606 caninclude filter circuitry 606 c and mixer circuitry 606 a. The RFcircuitry 606 also includes synthesizer circuitry 606 d for synthesizinga frequency for use by the mixer circuitry 606 a of the receive signalpath and the transmit signal path. In some implementations, the mixercircuitry 606 a of the receive signal path may be configured todown-convert RF signals received from the FEM circuitry 608 based on thesynthesized frequency provided by synthesizer circuitry 606 d. Theamplifier circuitry 606 b may be configured to amplify thedown-converted signals and the filter circuitry 606 c may be a low-passfilter (LPF) or band-pass filter (BPF) configured to remove unwantedsignals from the down-converted signals to generate output basebandsignals. Output baseband signals may be provided to the basebandcircuitry 610 for further processing. In some implementations, theoutput baseband signals may be zero-frequency baseband signals, althoughthis is not a requirement. In some implementations, the mixer circuitry606 a of the receive signal path may comprise passive mixers.

In some implementations, the mixer circuitry 606 a of the transmitsignal path may be configured to up-convert input baseband signals basedon the synthesized frequency provided by the synthesizer circuitry 606 dto generate RF output signals for the FEM circuitry 608. The basebandsignals may be provided by the baseband circuitry 610 and may befiltered by filter circuitry 606 c.

In some implementations, the mixer circuitry 606 a of the receive signalpath and the mixer circuitry 606 a of the transmit signal path caninclude two or more mixers and may be arranged for quadraturedownconversion and upconversion, respectively. In some implementations,the mixer circuitry 606 a of the receive signal path and the mixercircuitry 606 a of the transmit signal path can include two or moremixers and may be arranged for image rejection (e.g., Hartley imagerejection). In some implementations, the mixer circuitry 606 a of thereceive signal path and the mixer circuitry 606 a of the transmit signalpath may be arranged for direct downconversion and direct upconversion,respectively. In some implementations, the mixer circuitry 606 a of thereceive signal path and the mixer circuitry 606 a of the transmit signalpath may be configured for super-heterodyne operation.

In some implementations, the output baseband signals and the inputbaseband signals may be analog baseband signals. In someimplementations, the output baseband signals and the input basebandsignals may be digital baseband signals, and the RF circuitry 606 caninclude analog-to-digital converter (ADC) and digital-to-analogconverter (DAC) circuitry and the baseband circuitry 610 can include adigital baseband interface to communicate with the RF circuitry 606.

In some dual-mode examples, a separate radio IC circuitry may beprovided for processing signals for each spectrum, although thetechniques described here are not limited in this respect.

In some implementations, the synthesizer circuitry 606 d may be afractional-N synthesizer or a fractional N/N+1 synthesizer, althoughother types of frequency synthesizers may used. For example, synthesizercircuitry 606 d may be a delta-sigma synthesizer, a frequencymultiplier, or a synthesizer comprising a phase-locked loop with afrequency divider.

The synthesizer circuitry 606 d may be configured to synthesize anoutput frequency for use by the mixer circuitry 606 a of the RFcircuitry 606 based on a frequency input and a divider control input. Insome implementations, the synthesizer circuitry 606 d may be afractional N/N+1 synthesizer.

In some implementations, frequency input may be provided by a voltagecontrolled oscillator (VCO), although that is not a requirement. Dividercontrol input may be provided by either the baseband circuitry 610 orthe application circuitry 405/505 depending on the desired outputfrequency. In some implementations, a divider control input (e.g., N)may be determined from a look-up table based on a channel indicated bythe application circuitry 405, 505.

The synthesizer circuitry 606 d of the RF circuitry 606 can include adivider, a delay-locked loop (DLL), a multiplexer and a phaseaccumulator. In some implementations, the divider may be a dual modulusdivider (DMD) and the phase accumulator may be a digital phaseaccumulator (DPA). In some implementations, the DMD may be configured todivide the input signal by either N or N+1 (e.g., based on a carry out)to provide a fractional division ratio. In some implementations, the DLLcan include a set of cascaded, tunable, delay elements, a phasedetector, a charge pump and a D-type flip-flop. The delay elements maybe configured to break a VCO period up into Nd equal packets of phase,where Nd is the number of delay elements in the delay line. In this way,the DLL provides negative feedback to help ensure that the total delaythrough the delay line is one VCO cycle.

In some implementations, synthesizer circuitry 606 d may be configuredto generate a carrier frequency as the output frequency, while in otherexamples, the output frequency may be a multiple of the carrierfrequency (e.g., twice the carrier frequency, four times the carrierfrequency) and used in conjunction with quadrature generator and dividercircuitry to generate multiple signals at the carrier frequency withmultiple different phases with respect to each other. In someimplementations, the output frequency may be a LO frequency (fLO). Insome implementations, the RF circuitry 606 can include an IQ or polarconverter.

The FEM circuitry 608 can include a receive signal path, which caninclude circuitry configured to operate on RF signals received fromantenna array 611, amplify the received signals and provide theamplified versions of the received signals to the RF circuitry 606 forfurther processing. The FEM circuitry 608 may also include a transmitsignal path, which can include circuitry configured to amplify signalsfor transmission provided by the RF circuitry 606 for transmission byone or more of antenna elements of antenna array 611. The amplificationthrough the transmit or receive signal paths may be done solely in theRF circuitry 606, solely in the FEM circuitry 608, or in both the RFcircuitry 606 and the FEM circuitry 608.

In some implementations, the FEM circuitry 608 can include a TX/RXswitch to switch between transmit mode and receive mode operation. TheFEM circuitry 608 can include a receive signal path and a transmitsignal path. The receive signal path of the FEM circuitry 608 caninclude an LNA to amplify received RF signals and provide the amplifiedreceived RF signals as an output (e.g., to the RF circuitry 606). Thetransmit signal path of the FEM circuitry 608 can include a poweramplifier (PA) to amplify input RF signals (e.g., provided by RFcircuitry 606), and one or more filters to generate RF signals forsubsequent transmission by one or more antenna elements of the antennaarray 611.

The antenna array 611 comprises one or more antenna elements, each ofwhich is configured convert electrical signals into radio waves totravel through the air and to convert received radio waves intoelectrical signals. For example, digital baseband signals provided bythe baseband circuitry 610 is converted into analog RF signals (e.g.,modulated waveform) that will be amplified and transmitted using theantenna elements of the antenna array 611 including one or more antennaelements (not shown). The antenna elements may be omnidirectional,directional, or a combination thereof. The antenna elements may beformed in a multitude of arranges as are known and/or discussed herein.The antenna array 611 may comprise microstrip antennas or printedantennas that are fabricated on the surface of one or more printedcircuit boards. The antenna array 611 may be formed as a patch of metalfoil (e.g., a patch antenna) in a variety of shapes, and may be coupledwith the RF circuitry 606 and/or FEM circuitry 608 using metaltransmission lines or the like.

Processors of the application circuitry 405/505 and processors of thebaseband circuitry 610 may be used to execute elements of one or moreinstances of a protocol stack. For example, processors of the basebandcircuitry 610, alone or in combination, may execute Layer 3, Layer 2, orLayer 1 functionality, while processors of the application circuitry405, 505 may utilize data (e.g., packet data) received from these layersand further execute Layer 4 functionality (e.g., TCP and UDP layers). Asreferred to herein, Layer 3 may comprise a RRC layer, described infurther detail below. As referred to herein, Layer 2 may comprise a MAClayer, an RLC layer, and a PDCP layer, described in further detailbelow. As referred to herein, Layer 1 may comprise a PHY layer of aUE/RAN node, described in further detail below.

FIG. 7 illustrates example components of communication circuitry 700. Insome implementations, the communication circuitry 700 may be implementedas part of the system 400 or the platform 500 shown in FIGS. 4 and 5.The communication circuitry 700 may be communicatively coupled (e.g.,directly or indirectly) to one or more antennas, such as antennas 711A,711B, 711C, and 711D. In some implementations, the communicationcircuitry 700 includes or is communicatively coupled to dedicatedreceive chains, processors, or radios, or combinations of them, formultiple RATs (e.g., a first receive chain for LTE and a second receivechain for 5G NR). For example, as shown in FIG. 7, the communicationcircuitry 700 includes a modem 710 and a modem 720, which may correspondto or be a part of the baseband circuitry 410 and 510 of FIGS. 4 and 5.The modem 710 may be configured for communications according to a firstRAT, such as LTE or LTE-A, and the modem 720 may be configured forcommunications according to a second RAT, such as 5G NR. In someimplementations, a processor 705, such as an application processor, caninterface with the modems 710, 720.

The modem 710 includes one or more processors 712 and a memory 716 incommunication with the processors 712. The modem 710 is in communicationwith a radio frequency (RF) front end 730, which may correspond to or bea part of to the RFEM 415 and 515 of FIGS. 4 and 5. The RF front end 730can include circuitry for transmitting and receiving radio signals. Forexample, the RF front end 730 includes receive circuitry (RX) 732 andtransmit circuitry (TX) 734. In some implementations, the receivecircuitry 732 is in communication with a DL front end 752, which caninclude circuitry for receiving radio signals from one or more antennas711A. The transmit circuitry 734 is in communication with a UL front end754, which is coupled with one or more antennas 711B.

Similarly, the modem 720 includes one or more processors 722 and amemory 726 in communication with the one or more processors 722. Themodem 720 is in communication with an RF front end 740, which maycorrespond to or be a part of to the RFEM 415 and 515 of FIGS. 4 and 5.The RF front end 740 can include circuitry for transmitting andreceiving radio signals. For example, the RF front end 740 includesreceive circuitry 742 and transmit circuitry 744. In someimplementations, the receive circuitry 742 is in communication with a DLfront end 760, which can include circuitry for receiving radio signalsfrom one or more antennas 711C. The transmit circuitry 744 is incommunication with a UL front end 765, which is coupled with one or moreantennas 711D. In some implementations, one or more front-ends can becombined. For example, a RF switch can selectively couple the modems710, 720 to a single UL front end 772 for transmitting radio signalsusing one or more antennas.

The processors 712, 722 can include one or more processing elementsconfigured to implement various features described herein, such as byexecuting program instructions stored on the memory 716, 726 (e.g., anon-transitory computer-readable memory medium). In someimplementations, the processor 712, 722 may be configured as aprogrammable hardware element, such as a FPGA or an ASIC. In someimplementations, the processors 712, 722 can include one or more ICsthat are configured to perform the functions of processors 712, 722.

FIG. 8 illustrates various protocol functions that may be implemented ina wireless communication device. In particular, FIG. 8 includes anarrangement 800 showing interconnections between various protocollayers/entities. The following description of FIG. 8 is provided forvarious protocol layers and entities that operate in conjunction withthe 5G NR system standards and the LTE system standards, but some or allof the aspects of FIG. 8 may be applicable to other wirelesscommunication network systems as well.

The protocol layers of arrangement 800 can include one or more of PHY810, MAC 820, RLC 830, PDCP 840, SDAP 847, RRC 855, and NAS layer 857,in addition to other higher layer functions not illustrated. Theprotocol layers can include one or more service access points (e.g.,items 859, 856, 850, 849, 845, 835, 825, and 815 in FIG. 8) that mayprovide communication between two or more protocol layers.

The PHY 810 may transmit and receive physical layer signals 805 that maybe received from or transmitted to one or more other communicationdevices. The physical layer signals 805 can include one or more physicalchannels, such as those discussed herein. The PHY 810 may furtherperform link adaptation or adaptive modulation and coding (AMC), powercontrol, cell search (e.g., for initial synchronization and handoverpurposes), and other measurements used by higher layers, such as the RRC855. The PHY 810 may still further perform error detection on thetransport channels, forward error correction (FEC) coding and decodingof the transport channels, modulation and demodulation of physicalchannels, interleaving, rate matching, mapping onto physical channels,and MIMO antenna processing. In some implementations, an instance of PHY810 may process requests from and provide indications to an instance ofMAC 820 using one or more PHY-SAP 815. In some implementations, requestsand indications communicated using PHY-SAP 815 may comprise one or moretransport channels.

Instance(s) of MAC 820 may process requests from, and provideindications to, an instance of RLC 830 using one or more MAC-SAPs 825.These requests and indications communicated using the MAC-SAP 825 caninclude one or more logical channels. The MAC 820 may perform mappingbetween the logical channels and transport channels, multiplexing of MACSDUs from one or more logical channels onto transport blocks (TBs) to bedelivered to PHY 810 using the transport channels, de-multiplexing MACSDUs to one or more logical channels from TBs delivered from the PHY 810using transport channels, multiplexing MAC SDUs onto TBs, schedulinginformation reporting, error correction through HARQ, and logicalchannel prioritization.

Instance(s) of RLC 830 may process requests from and provide indicationsto an instance of PDCP 840 using one or more radio link control serviceaccess points (RLC-SAP) 835. These requests and indications communicatedusing RLC-SAP 835 can include one or more RLC channels. The RLC 830 mayoperate in a plurality of modes of operation, including: TransparentMode™, Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC 830may execute transfer of upper layer protocol data units (PDUs), errorcorrection through automatic repeat request (ARQ) for AM data transfers,and concatenation, segmentation and reassembly of RLC SDUs for UM and AMdata transfers. The RLC 830 may also execute re-segmentation of RLC dataPDUs for AM data transfers, reorder RLC data PDUs for UM and AM datatransfers, detect duplicate data for UM and AM data transfers, discardRLC SDUs for UM and AM data transfers, detect protocol errors for AMdata transfers, and perform RLC re-establishment.

Instance(s) of PDCP 840 may process requests from and provideindications to instance(s) of RRC 855 or instance(s) of SDAP 847, orboth, using one or more packet data convergence protocol service accesspoints (PDCP-SAP) 845. These requests and indications communicated usingPDCP-SAP 845 can include one or more radio bearers. The PDCP 840 mayexecute header compression and decompression of IP data, maintain PDCPSequence Numbers (SNs), perform in-sequence delivery of upper layer PDUsat re-establishment of lower layers, eliminate duplicates of lower layerSDUs at re-establishment of lower layers for radio bearers mapped on RLCAM, cipher and decipher control plane data, perform integrity protectionand integrity verification of control plane data, control timer-baseddiscard of data, and perform security operations (e.g., ciphering,deciphering, integrity protection, or integrity verification).

Instance(s) of SDAP 847 may process requests from and provideindications to one or more higher layer protocol entities using one ormore SDAP-SAP 849. These requests and indications communicated usingSDAP-SAP 849 can include one or more QoS flows. The SDAP 847 may map QoSflows to data radio bearers (DRBs), and vice versa, and may also markQoS flow identifiers (QFIs) in DL and UL packets. A single SDAP entity847 may be configured for an individual PDU session. In the ULdirection, the NG-RAN 110 may control the mapping of QoS Flows to DRB(s)in two different ways, reflective mapping or explicit mapping. Forreflective mapping, the SDAP 847 of a UE 101 may monitor the QFIs of theDL packets for each DRB, and may apply the same mapping for packetsflowing in the UL direction. For a DRB, the SDAP 847 of the UE 101 maymap the UL packets belonging to the QoS flows(s) corresponding to theQoS flow ID(s) and PDU session observed in the DL packets for that DRB.To enable reflective mapping, the NG-RAN 310 may mark DL packets overthe Uu interface with a QoS flow ID. The explicit mapping may involvethe RRC 855 configuring the SDAP 847 with an explicit QoS flow to DRBmapping rule, which may be stored and followed by the SDAP 847. In someimplementations, the SDAP 847 may only be used in NR implementations andmay not be used in LTE implementations.

The RRC 855 may configure, using one or more management service accesspoints (M-SAP), aspects of one or more protocol layers, which caninclude one or more instances of PHY 810, MAC 820, RLC 830, PDCP 840 andSDAP 847. In some implementations, an instance of RRC 855 may processrequests from and provide indications to one or more NAS entities 857using one or more RRC-SAPs 856. The main services and functions of theRRC 855 can include broadcast of system information (e.g., included inmaster information blocks (MIBs) or system information blocks (SIBs)related to the NAS), broadcast of system information related to theaccess stratum (AS), paging, establishment, maintenance and release ofan RRC connection between the UE 101 and RAN 110 (e.g., RRC connectionpaging, RRC connection establishment, RRC connection modification, andRRC connection release), establishment, configuration, maintenance andrelease of point to point Radio Bearers, security functions includingkey management, inter-RAT mobility, and measurement configuration for UEmeasurement reporting. The MIBs and SIBs may comprise one or moreinformation elements, which may each comprise individual data fields ordata structures.

The NAS 857 may form the highest stratum of the control plane betweenthe UE 101 and the AMF 321. The NAS 857 may support the mobility of theUEs 101 and the session management procedures to establish and maintainIP connectivity between the UE 101 and a P-GW in LTE systems.

In some implementations, one or more protocol entities of arrangement800 may be implemented in UEs 101, RAN nodes 111, AMF 321 in NRimplementations or MME 221 in LTE implementations, UPF 302 in NRimplementations or S-GW 222 and P-GW 223 in LTE implementations, or thelike to be used for control plane or user plane communications protocolstack between the aforementioned devices. In some implementations, oneor more protocol entities that may be implemented in one or more of UE101, gNB 111, AMF 321, among others, may communicate with a respectivepeer protocol entity that may be implemented in or on another deviceusing the services of respective lower layer protocol entities toperform such communication. In some implementations, a gNB-CU of the gNB111 may host the RRC 855, SDAP 847, and PDCP 840 of the gNB thatcontrols the operation of one or more gNB-DUs, and the gNB-DUs of thegNB 111 may each host the RLC 830, MAC 820, and PHY 810 of the gNB 111.

In some implementations, a control plane protocol stack can include, inorder from highest layer to lowest layer, NAS 857, RRC 855, PDCP 840,RLC 830, MAC 820, and PHY 810. In this example, upper layers 860 may bebuilt on top of the NAS 857, which includes an IP layer 861, an SCTP862, and an application layer signaling protocol (AP) 863.

In some implementations, such as NR implementations, the AP 863 may bean NG application protocol layer (NGAP or NG-AP) 863 for the NGinterface 113 defined between the NG-RAN node 111 and the AMF 321, orthe AP 863 may be an Xn application protocol layer (XnAP or Xn-AP) 863for the Xn interface 112 that is defined between two or more RAN nodes111.

The NG-AP 863 may support the functions of the NG interface 113 and maycomprise elementary procedures (EPs). An NG-AP EP may be a unit ofinteraction between the NG-RAN node 111 and the AMF 321. The NG-AP 863services can include two groups: UE-associated services (e.g., servicesrelated to a UE 101) and non-UE-associated services (e.g., servicesrelated to the whole NG interface instance between the NG-RAN node 111and AMF 321). These services can include functions such as, but notlimited to: a paging function for the sending of paging requests toNG-RAN nodes 111 involved in a particular paging area; a UE contextmanagement function for allowing the AMF 321 to establish, modify, orrelease a UE context in the AMF 321 and the NG-RAN node 111; a mobilityfunction for UEs 101 in ECM-CONNECTED mode for intra-system HOs tosupport mobility within NG-RAN and inter-system HOs to support mobilityfrom/to EPS systems; a NAS Signaling Transport function for transportingor rerouting NAS messages between UE 101 and AMF 321; a NAS nodeselection function for determining an association between the AMF 321and the UE 101; NG interface management function(s) for setting up theNG interface and monitoring for errors over the NG interface; a warningmessage transmission function for providing means to transfer warningmessages using NG interface or cancel ongoing broadcast of warningmessages; a configuration transfer function for requesting andtransferring of RAN configuration information (e.g., SON information orperformance measurement (PM) data) between two RAN nodes 111 using CN120, or combinations of them, among others.

The XnAP 863 may support the functions of the Xn interface 112 and maycomprise XnAP basic mobility procedures and XnAP global procedures. TheXnAP basic mobility procedures may comprise procedures used to handle UEmobility within the NG RAN 111 (or E-UTRAN 210), such as handoverpreparation and cancellation procedures, SN Status Transfer procedures,UE context retrieval and UE context release procedures, RAN pagingprocedures, or dual connectivity related procedures, among others. TheXnAP global procedures may comprise procedures that are not related to aspecific UE 101, such as Xn interface setup and reset procedures, NG-RANupdate procedures, or cell activation procedures, among others.

In LTE implementations, the AP 863 may be an S1 Application Protocollayer (S1-AP) 863 for the S1 interface 113 defined between an E-UTRANnode 111 and an MME, or the AP 863 may be an X2 application protocollayer (X2AP or X2-AP) 863 for the X2 interface 112 that is definedbetween two or more E-UTRAN nodes 111.

The S1 Application Protocol layer (S1-AP) 863 may support the functionsof the S1 interface, and similar to the NG-AP discussed previously, theS1-AP can include S1-AP EPs. An S1-AP EP may be a unit of interactionbetween the E-UTRAN node 111 and an MME 221 within an LTE CN 120. TheS1-AP 863 services may comprise two groups: UE-associated services andnon UE-associated services. These services perform functions including,but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UEcapability indication, mobility, NAS signaling transport, RANInformation Management (RIM), and configuration transfer.

The X2AP 863 may support the functions of the X2 interface 112 and caninclude X2AP basic mobility procedures and X2AP global procedures. TheX2AP basic mobility procedures can include procedures used to handle UEmobility within the E-UTRAN 120, such as handover preparation andcancellation procedures, SN Status Transfer procedures, UE contextretrieval and UE context release procedures, RAN paging procedures, ordual connectivity related procedures, among others. The X2AP globalprocedures may comprise procedures that are not related to a specific UE101, such as X2 interface setup and reset procedures, load indicationprocedures, error indication procedures, or cell activation procedures,among others.

The SCTP layer (alternatively referred to as the SCTP/IP layer) 862 mayprovide guaranteed delivery of application layer messages (e.g., NGAP orXnAP messages in NR implementations, or S1-AP or X2AP messages in LTEimplementations). The SCTP 862 may ensure reliable delivery of signalingmessages between the RAN node 111 and the AMF 321/MME 221 based in parton the IP protocol, supported by the IP 861. The Internet Protocol layer(IP) 861 may be used to perform packet addressing and routingfunctionality. In some implementations the IP layer 861 may usepoint-to-point transmission to deliver and convey PDUs. In this regard,the RAN node 111 can include L2 and L1 layer communication links (e.g.,wired or wireless) with the MME/AMF to exchange information.

In some implementations, a user plane protocol stack can include, inorder from highest layer to lowest layer, SDAP 847, PDCP 840, RLC 830,MAC 820, and PHY 810. The user plane protocol stack may be used forcommunication between the UE 101, the RAN node 111, and UPF 302 in NRimplementations or an S-GW 222 and P-GW 223 in LTE implementations. Inthis example, upper layers 851 may be built on top of the SDAP 847, andcan include a user datagram protocol (UDP) and IP security layer(UDP/IP) 852, a General Packet Radio Service (GPRS) Tunneling Protocolfor the user plane layer (GTP-U) 853, and a User Plane PDU layer (UPPDU) 863.

The transport network layer 854 (also referred to as a “transportlayer”) may be built on IP transport, and the GTP-U 853 may be used ontop of the UDP/IP layer 852 (comprising a UDP layer and IP layer) tocarry user plane PDUs (UP-PDUs). The IP layer (also referred to as the“Internet layer”) may be used to perform packet addressing and routingfunctionality. The IP layer may assign IP addresses to user data packetsin any of IPv4, IPv6, or PPP formats, for example.

The GTP-U 853 may be used for carrying user data within the GPRS corenetwork and between the radio access network and the core network. Theuser data transported can be packets in any of IPv4, IPv6, or PPPformats, for example. The UDP/IP 852 may provide checksums for dataintegrity, port numbers for addressing different functions at the sourceand destination, and encryption and authentication on the selected dataflows. The RAN node 111 and the S-GW 222 may utilize an S1-U interfaceto exchange user plane data using a protocol stack comprising an L1layer (e.g., PHY 810), an L2 layer (e.g., MAC 820, RLC 830, PDCP 840,and/or SDAP 847), the UDP/IP layer 852, and the GTP-U 853. The S-GW 222and the P-GW 223 may utilize an S5/S8a interface to exchange user planedata using a protocol stack comprising an L1 layer, an L2 layer, theUDP/IP layer 852, and the GTP-U 853. As discussed previously, NASprotocols may support the mobility of the UE 101 and the sessionmanagement procedures to establish and maintain IP connectivity betweenthe UE 101 and the P-GW 223.

Moreover, although not shown by FIG. 8, an application layer may bepresent above the AP 863 and/or the transport network layer 854. Theapplication layer may be a layer in which a user of the UE 101, RAN node111, or other network element interacts with software applications beingexecuted, for example, by application circuitry 405 or applicationcircuitry 505, respectively. The application layer may also provide oneor more interfaces for software applications to interact withcommunications systems of the UE 101 or RAN node 111, such as thebaseband circuitry 610. In some implementations, the IP layer or theapplication layer, or both, may provide the same or similarfunctionality as layers 5-7, or portions thereof, of the Open SystemsInterconnection (OSI) model (e.g., OSI Layer 7—the application layer,OSI Layer 6—the presentation layer, and OSI Layer 5—the session layer).

NFV architectures and infrastructures may be used to virtualize one ormore NFs, alternatively performed by proprietary hardware, onto physicalresources comprising a combination of industry-standard server hardware,storage hardware, or switches. In other words, NFV systems can be usedto execute virtual or reconfigurable implementations of one or more EPCcomponents and functions.

FIG. 9 illustrates a block diagram of example of a computer system thatincludes components for reading instructions from a machine-readable orcomputer-readable medium (e.g., a non-transitory machine-readablestorage medium) and performing any one or more of the techniquesdescribed herein. In this example, FIG. 9 shows a diagrammaticrepresentation of hardware resources 900 including one or moreprocessors (or processor cores) 910, one or more memory or storagedevices 920, and one or more communication resources 930, each of whichmay be communicatively coupled using a bus 940. For implementationswhere node virtualization (e.g., NFV) is utilized, a hypervisor 902 maybe executed to provide an execution environment for one or more networkslices or sub-slices to utilize the hardware resources 900.

The processors 910 can include a processor 912 and a processor 914. Theprocessor(s) 910 may be, for example, a central processing unit (CPU), areduced instruction set computing (RISC) processor, a complexinstruction set computing (CISC) processor, a graphics processing unit(GPU), a DSP such as a baseband processor, an ASIC, an FPGA, aradio-frequency integrated circuit (RFIC), another processor (includingthose discussed herein), or any suitable combination thereof.

The memory/storage devices 920 can include main memory, disk storage, orany suitable combination thereof. The memory/storage devices 920 caninclude, but are not limited to, any type of volatile or nonvolatilememory such as dynamic random access memory (DRAM), static random accessmemory (SRAM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), Flashmemory, or solid-state storage, or combinations of them, among others.

The communication resources 930 can include interconnection or networkinterface components or other suitable devices to communicate with oneor more peripheral devices 904 or one or more databases 906 using anetwork 908. For example, the communication resources 930 can includewired communication components (e.g., for coupling using USB), cellularcommunication components, NFC components, Bluetooth® (or Bluetooth® LowEnergy) components, Wi-Fi components, and other communicationcomponents.

Instructions 950 may comprise software, a program, an application, anapplet, an app, or other executable code for causing at least any of theprocessors 910 to perform any one or more of the methodologies discussedherein. The instructions 950 may reside, completely or partially, withinat least one of the processors 910 (e.g., within the processor's cachememory), the memory/storage devices 920, or any suitable combinationthereof. Furthermore, any portion of the instructions 950 may betransferred to the hardware resources 900 from any combination of theperipheral devices 904 or the databases 906. Accordingly, the memory ofprocessors 910, the memory/storage devices 920, the peripheral devices904, and the databases 906 are examples of computer-readable andmachine-readable media.

A UE can use control information transmitted by a base station to decodea downlink channel such as a PDSCH. Further, wireless networks can useone or more precoding techniques for PDSCH including those based on PRBbundling. Precoding can be based on a frequency domain granularity,where a precoding procedure is applied across multiple PRBs. The UE canassume that the same precoding technique is applied to a set of bundledPRBs, which are contiguous. To decode PDSCH, the UE should have anassumption on the precoder granularity in the frequency domain, so as todecide the channel estimation granularity in the frequency domain.

A downlink transmission, such as those on PDSCH, can occur in one ormore bandwidth parts (BWPs). A BWP can include a set of contiguousresource blocks such as PRBs. A BWP can be partitioned into PrecodingResource block Groups (PRGs). A UE can assume that the same precoder isapplied for a PRG. In 3GPP Rel-15, PRB bundling is described as tomaintain the same understanding between gNB and UE on the precodergranularity, e.g., the UE and gNB can operate based on using or derivingthe same PRG size. A PRG size can also be referred to as a PRB bundlingsize. In some implementations, candidate values for the PRG size caninclude two resource blocks (2RB), four resource blocks (4RB), or awideband value. In some implementations, the size of PRG can beconfigured in part by RRC or a combination of RRC and DCI with acandidate value selected from a group including 2RB, 4RB, and widebandvalues. Other and more types of values are possible. In someimplementations, a wideband value indicates a larger group of resourceblocks, e.g., more than four blocks.

FIG. 10 illustrates a flowchart of an example procedure for deriving aPRG size. At 1005, the UE receives control signal information. Controlsignal information can include DCI and one or more RRC parameters suchas prb-BundleType, bundleSize, bundleSizeSet1, or bundleSizeSet2. Othertypes of RRC parameters are possible. At 1010, the UE determines if thePDSCH is scheduled by DCI format 1_0. If yes, then the PRG size is setto two at 1015, and the process concludes.

At 1020, the UE determines if RRC parameter prb-BundleType isconfigured. If no, then the PRG size is set to two at 1015, and theprocess concludes.

At 1025, the UE determines if the value of RRC parameter prb-BundleTypeequals dynamicBundling. If it is not equal, then the PRG size isconfigured by higher layer parameter bundleSize at 1030, and the processconcludes.

At 1035, the UE determines if value of DCI field PRB bundling sizeindicator equals zero. If it is not equal, then the PRG size isconfigured by higher layer parameter bundleSizeSet2 at 1030, and theprocess concludes.

At 1045, the UE determines if one value is configured in higher layerparameter bundleSizeSet1. If yes, the PRG size is configured by higherlayer parameter bundleSizeSet1 at 1050, and the process concludes.

At 1055, the UE determines if scheduled PRB is contiguous and number ofscheduled PRBs is above half of bandwidth of active BWP. If it is notabove, then the PRG size is set to 2 or 4 as configured by higher layerparameter bundleSizeSet1 at 1060, and the process concludes. If it isabove, the PRG size is set to wideband. In some implementations, theprocess illustrated in FIG. 10 can be modified to support PDSCHtransmission from multiple TRPs.

3GPP Rel-16 and beyond provides support for multiple TRPs. In amulti-TRP operation, a channel such as PDSCH can be transmitted frommultiple TRPs. PDSCH transmissions can be scheduled by a DCI message ormultiple DCI messages. In this disclosure, techniques for controlsignaling of the PRG size configuration for multi-TRP operation areproposed including: a technique for signaling a PRG size indication fora single DCI based operation and a technique for signaling a PRG sizeindication for a multi-DCI based operation.

FIG. 11 illustrates an example of a multi-TRP operation 1101. Themulti-TRP operation 1101 can include PDSCH transmissions 1121, 1122,1123, and 1124 from multiple TRPs (labeled TRP 1, TRP 2, and TRP 3) overone or more frequency resources, spatial resources, time, or acombination thereof. In some implementations, TRPs 1, 2, and 3correspond to different gNBs. In some implementations, a gNB can beassociated with more than one TRP. In some implementations, a given setof PDSCH transmissions 1121, 1122, 1123, and 1124 can be scheduled by asingle DCI. In some implementations, a given set of PDSCH transmissions1121, 1122, 1123, and 1124 can be scheduled by multiple DCIs.

A PDSCH transmission 1121, 1122, 1123, and 1124 can include one or morePRBs. PRBs corresponding to the PDSCH transmissions 1121, 1122, 1123,and 1124 can overlap. In this example, PRBs corresponding to PDSCHtransmissions 1121 and 1122 fully overlap with each other in thefrequency domain, while being in different spatial domain layers. ThePRB corresponding to PDSCH transmission 1123 partially overlap with someother PRBs, e.g., PRBs corresponding to PDSCH transmissions 1121 and1122, and does not overlap with others, e.g., PRB corresponding to PDSCHtransmission 1124. The given arrangement of transmissions in FIG. 11 isan example. Other arrangements are possible.

Because the resource blocks of PDSCH transmissions can originate fromdifferent TRPs, such as illustrated in FIG. 11, scheduled PRBs can bedivided into two or more sets of PRBs associated with differenttransmission configuration indicator (TCI) states. Such TCI states canprovide different quasi-co-location (QCL) information to the UE. QCLinformation can help in determining one or more channel properties. In3GPP, two antenna ports are said to be quasi co-located if properties ofthe channel over which a symbol on one antenna port is conveyed can beinferred from the channel over which a symbol on the other antenna portis conveyed.

PRBs associated with one or more TCI states can be multiplexed in one ormore ways, e.g., Time Division Multiplexing (TDM), Frequency DivisionMultiplexing (FDM), Spatial Division Multiplexing (SDM), or combinationsthereof. In some implementations, when FDM or FDM/SDM multiplexing isused, UE can be configured to not assume that a precoder is constantacross all scheduled PRBs, since the equivalent channel for differentsets of PRBs corresponds to different TRPs is different as a result ofdifferent QCL information as shown for example in FIG. 11.

FIG. 12 illustrates a flowchart of an example of a decoding processassociated with a multi-TRP operation. The process can be implemented bya UE. At 1205, the UE receives a DCI message(s) that provides schedulingfor PDSCH. In some implementations, the DCI message(s) can provide a PRGsize indication. In some implementations, a base station, such as a gNB,can provide a PRG size indication in a single DCI based operation, e.g.,a single DCI message, for PDSCH transmissions from multiple TRPs. Insome implementations, a base station, such as a gNB, can provide a PRGsize indication in a multi-DCI based operation, e.g., multiple DCImessages, for PDSCH transmissions from multiple TRPs.

At 1210, the UE determines a PRG size based on the DCI message(s).Determining the PRG size can include determining if a bundle typeparameter specifies a dynamic bundling attribute. In someimplementations, determining the PRG size can include determining if thePRBs associated with the different TCI states are non-overlapping or atleast partially overlapping. Determining the PRG size can includedetermining if a bundle size set parameter contains two or more bundlesize parameters. Determining the PRG size can include determining if atleast a portion of the PRBs are contiguous. Determining the PRG size caninclude determining whether at least a portion of the PDSCHtransmissions are multiplexed in frequency, space, or both.

In some implementations, determining the PRG size can includedetermining a quantity of TCI states in a codepoint of the DCI fieldTransmission Configuration Indication in a DCI message. Determining thePRG size can include determining if the PRG size is wideband or notwideband, e.g., subband. PRBs can be assigned to different TCI states.In some implementations, if the PRG size is determined as wideband, thefirst

$\left\lceil \frac{n_{PRB}}{2} \right\rceil$

PRBs are assigned to the first TCI state and the remaining

$\left\lfloor \frac{n_{PRB}}{2} \right\rfloor$

PRBs are assigned to the second TCI state, where n_(PRB) is the totalnumber of allocated PRBs for the UE. In some implementations, if the PRGsize is determined as subband, e.g. 2 or 4 PRBs per PRG, the even PRGswithin the allocated frequency domain resources are assigned to thefirst TCI state and odd PRGs within the allocated frequency domainresources are assigned to the second TCI state.

In some implementations, if two or more DCI messages provide schedulinginformation for a group of PDSCH transmissions, the UE can determinethat a PRG size is equal to wideband based on the two or more DCImessages. Determining that the PRG size is equal to wideband can includedetermining whether a bandwidth of a total number of PRBs scheduled bythe two or more DCI messages is above half of a bandwidth of an activebandwidth part.

At 1215, the UE receives a group of PDSCH transmissions from multipleTRPs that are transmitted in accordance with the DCI message(s).Receiving the group of PDSCH transmissions can include receiving PRBsthat are associated with different TCI states, which are respectivelyassociated with the multiple TRPs. In some implementations, receivingPRBs that are associated with different TCI states can include receivinga first PRB set associated with a first TCI state, and receiving asecond PRB set associated with a second TCI states. A PRB set caninclude one or more PRBs.

At 1220, the UE decodes one or more of the PDSCH transmissions based onthe PRG size. Decoding one or more of the PDSCH transmissions based onthe PRG size can include applying a precoding technique based on the PRGsize. In some implementations, the UE can determine that a precoder forat least one of the PDSCH transmissions is constant or wideband if PRBsassociated with different TCI states are non-overlapping.

A base station, such as a gNB, can provide a PRG size indication in asingle DCI based operation, e.g., a single DCI message, for PDSCHtransmissions from multiple TRPs. In some implementations, a UE usesinformation from the DCI message and RRC layer to determine a PRG size.A UE can, for example, make a PRG size determination based on whetherscheduled PRBs corresponding to PDSCH transmissions overlap. In someimplementations, if UE is scheduled with PDSCH from multi-TRP (e.g. morethan one TCI state) where PRBs associated with different TCI states arepartially overlapping or non-overlapping, UE shall not expect the PRGsize to be configured or indicated as wideband. If the UE does notexpect the PRG size to be configured as wideband, then UE can configuredthe PRG size based on other factors such as a bundle size set specifiedby a higher layer such as RRC.

In some implementations, if PRG size is configured as wideband, and UEis scheduled with PDSCH from multiple TRPs (e.g., more than one TCIstate is indicated for the scheduled PDSCH) and PRBs set correspondingto different TCI state are non-overlapping, UE shall assume the precoderof the PDSCH from one TRP (or from the PRB set) is constant or wideband.In some implementations, the UE may assume wideband precoding for thePRB set corresponding to one TCI state only if the scheduled PRB set iscontiguous and spans half of the BW of the active BWP.

In some implementations, for PRB bundling type set as dynamic bundlingand when two values are configured in bundleSizeSet1, whether PRG sizeis wideband or not is determined by one or more of the followingconditions: whether PDSCH is scheduled from a single TRP or multipleTRPs, type of the multiplexing operation (e.g., SDM, FDM, TDM, or acombination thereof) of PRBs sets, whether the scheduled PRBs in PRB setare contiguous, number of scheduled PRBs for PDSCH from one TRP or allTRPs, bandwidth of an active bandwidth part, or a combination thereof

In one option, for PRB bundling type set as dynamic bundling and whentwo values are configured in bundleSizeSet1, if scheduled PDSCH is fromone TRP (e.g., associated with one TCI state), and the scheduled PRBsare contiguous, number of scheduled PRBs is above half of bandwidth ofactive bandwidth part, UE shall assume the PRG size equal to wideband;otherwise, UE shall assume the PRG size equal to 2 or 4 configured bybundleSizeSet1.

In another option, for PRB bundling type set as dynamic bundling andwhen two values are configured in bundleSizeSet1, if scheduled PDSCH isfrom one TRP (e.g., associated with one TCI state) or from multiple TRPs(e.g., associated with two or more TCI state) and scheduled PDSCH ismultiplexed in fully overlapped PRBs, and the scheduled PRB iscontiguous, number of scheduled PRBs is above half of bandwidth ofactive bandwidth part, UE shall assume the PRG size equal to wideband;otherwise, UE shall assume the PRG size equal to 2 or 4 configured bybundleSizeSet1.

In another option, for PRB bundling type set as dynamic bundling andwhen two values are configured in bundleSizeSet1, if scheduled PDSCH isfrom one TRP, e.g., associated with one TCI state) or from multiple TRPs(e.g., associated with two or more TCI state) and scheduled PDSCH ismultiplexed in fully overlapped PRBs or scheduled PDSCH is multiplexedin non-overlapped PRBs, and the scheduled PRBs for each PRB set iscontiguous, number of total scheduled PRBs or number of themaximum/minimum scheduled PRBs in PRB set for PDSCH from a TRP is abovehalf of bandwidth of active bandwidth part, UE shall assume the PRG sizeequal to wideband; otherwise, UE shall assume the PRG size equal to 2 or4 configured by a bundle size set parameter such as bundleSizeSet1.

One or more base stations can provide a PRG size indication in amulti-DCI based operation for PDSCH transmissions from multiple TRPs.For multi-DCI based operation, PDSCH transmissions from different TRPscan be scheduled by different DCIs. If the PDSCH is received from thesame UE antenna ports, some restriction on PRG size indication can berequired. In some implementations, UE shall expect that the PRG size forPDSCH scheduled by multiple DCIs should be the same. UE shall expect thevalue of PRB bundling size indicator in each DCI should be configured tobe the same if present.

In some implementations, a UE can make a PRG size determination based onall of the DCIs associated with the multi-DCI based operation. In someimplementations, for PRB bundling type set as dynamic bundling and whentwo values are configured in bundleSizeSet1, whether PRG size iswideband or not is determined by scheduled PRBs indicated by all DCIs aswell as the bandwidth of bandwidth part.

In one option, for PRB bundling type set as dynamic bundling and whentwo values are configured in bundleSizeSet1, if the scheduled PRB fromall DCIs is contiguous and total number of scheduled PRBs from all DCIsis above half of bandwidth of active bandwidth part, UE shall assume thePRG size equal to wideband; otherwise, UE shall assume the PRG sizeequal to 2 or 4 configured by bundleSizeSet1.

In another option, for PRB bundling type set as dynamic bundling andwhen two values are configured in bundleSizeSet1, if minimal or maximumthe scheduled PRB from all DCIs is contiguous and minimal or maximumnumber of scheduled PRBs from all DCIs is above half of bandwidth ofactive bandwidth part, UE shall assume the PRG size equal to wideband;otherwise, UE shall assume the PRG size equal to 2 or 4 configured bybundleSizeSet1. In some implementations, for PRB bundling type set asdynamic bundling and there is a multi-DCI operation, UE shall expectonly that one value is configured in a bundle size set parameter such asbundleSizeSet1.

A technique for operating a UE can include determining a PRB bundlingsize, which can be referred to as a PRG size, when scheduled with PDSCHfrom multiple TRPs. Multiple TRPs can be indicated by more than onetransmission configuration indicator. In some implementations, the PDSCHfrom multiple TRPs may be scheduled by one DCI. Decoding PDSCH caninclude decoding signals based on one or more PRB bundling sizes.

In some implementations, if UE is scheduled with PDSCH from multi-TRP(e.g., more than one TCI state) where PRBs associated with different TCIstates are partially overlapping or non-overlapping, UE shall not expectPRG size be configured or indicated as wideband. In someimplementations, if a PRG size is configured as wideband, and UE isscheduled with PDSCH from multiple TRP (e.g. more than one TCI state isindicated for the scheduled PDSCH) and PRB sets corresponding todifferent TCI states are non-overlapping, UE shall assume the precoderof the PDSCH from one TRP (or from one PRB set) is constant or wideband.In some implementations, UE may assume wideband precoding for the PRBset corresponding to one TCI state only if the scheduled PRB set iscontiguous and spans half of the BW of the active bandwidth part.

In some implementations, for when a PRB bundling type is set as dynamicbundling and when two values are configured in bundleSizeSet1, whether aPRG size is wideband or not is determined by at least one of thefollowing conditions: whether PDSCH is scheduled from single or multipleTRPs (e.g. associated with one or more than one TCI states), type of themultiplexing operation (e.g., SDM, FDM, TDM, etc.) of PRBs sets, whetherthe scheduled PRBs in PRB set are contiguous, number of scheduled PRBsfor PDSCH from one TRP or all TRPs, and bandwidth of an active bandwidthpart.

In some implementations, for when a PRB bundling type is set as dynamicbundling and when two values are configured in bundleSizeSet1, ifscheduled PDSCH is from one TRP (e.g., associated with one TCI state),and the scheduled PRBs are contiguous, number of scheduled PRBs is abovehalf of bandwidth of active bandwidth part, UE shall assume that the PRGsize is equal to wideband; otherwise, UE shall assume that the PRG sizeis equal to 2 or 4 as configured by bundleSizeSet1.

In some implementations, for when a PRB bundling type is set as dynamicbundling and when two values are configured in bundleSizeSet1, ifscheduled PDSCH is from one TRP (e.g., associated with one TCI state) orfrom multiple TRPs (e.g. associated with two or more TCI state) andscheduled PDSCH is multiplexed in fully overlapped PRBs, and thescheduled PRB is contiguous, number of scheduled PRBs is above half ofbandwidth of active bandwidth part, UE shall assume that the PRG size isequal to wideband; otherwise, UE shall assume that the PRG size is equalto 2 or 4 as configured by bundleSizeSet1.

In some implementations, for when a PRB bundling type is set as dynamicbundling and when two values are configured in bundleSizeSet1, ifscheduled PDSCH is from one TRP (e.g., associated with one TCI state) orfrom multiple TRPs (e.g., associated with two or more TCI states) andscheduled PDSCH is multiplexed in fully overlapped PRBs or scheduledPDSCH is multiplexed in non-overlapped PRBs, and the scheduled PRBs foreach PRB set is contiguous, number of total scheduled PRBs or number ofthe maximum/minimum scheduled PRBs in PRB set for PDSCH from a TRP isabove half of bandwidth of an active bandwidth part, UE shall assumethat the PRG size is equal to wideband; otherwise, UE shall assume thatthe PRG size is equal to 2 or 4 as configured by bundleSizeSet1. In someimplementations, scheduled PRBs can include a scheduled PRBcorresponding to a minimum PRB of a set and a scheduled PRBcorresponding to a maximum PRB of the set.

The PDSCH from multiple TRPs, in some implementations, may be scheduledby multiple DCIs. In some implementations, UE shall expect that the PRGsize for PDSCH scheduled by multiple DCI should be the same. In someimplementations, UE shall expect the value of PRB bundling sizeindicator in each DCI should be configured to be the same if present. Insome implementations, for when a PRB bundling type is set as dynamicbundling and when two values are configured in bundleSizeSet1, whetherPRG size is wideband or not is determined by scheduled PRBs indicated byall DCIs as well as the bandwidth of bandwidth part. In someimplementations, for when a PRB bundling type is set as dynamic bundlingand when two values are configured in bundleSizeSet1, if the scheduledPRB from all DCIs is contiguous and total number of scheduled PRBs fromall DCIs is above half of bandwidth of active bandwidth part, UE shallassume the PRG size equal to wideband; otherwise, UE shall assume thePRG size equal to 2 or 4 configured by bundleSizeSet1.

In some implementations, for when a PRB bundling type is set as dynamicbundling and when two values are configured in bundleSizeSet1, ifminimal or maximum the scheduled PRB from all DCIs is contiguous andminimal or maximum number of scheduled PRBs from all DCIs is above halfof bandwidth of active bandwidth part, UE shall assume the PRG sizeequal to wideband; otherwise, UE shall assume the PRG size equal to 2 or4 configured by bundleSizeSet1. In some implementations, for when a PRBbundling type is set as dynamic bundling and a multi-DCI operationoccurs, UE shall expect only one value is configured in bundleSizeSet1.

Another UE technique includes decoding one or more signals to determinea PRG size for a single-DCI or multi-DCI based operation; and decodingPDSCH based on the PRG size. In some implementations, the PDSCH istransmitted from multiple TRPs and scheduled by a single DCI. Thetechnique can include determining that the PRG size is not wideband ifPRBs associated with different TCI states are partially overlapping ornon-overlapping. The technique can include determining a precoding or ofthe PDSCH from one TRP (or PRB set) is constant or wideband if the UE isscheduled with PDSCH from multiple TRPs and PRB sets corresponding todifferent TCI states are non-overlapping. In some implementations, thePDSCH is transmitted from different TRPs and is scheduled by differentDCIs. The technique can include determining that a PRG size for PDSCHscheduled by different DCSs are the same.

These and other techniques can be performed by an apparatus that isimplemented in or employed by one or more types of network components,user devices, or both. In some implementations, one or morenon-transitory computer-readable media comprising instructions to causean electronic device, upon execution of the instructions by one or moreprocessors of the electronic device, to perform one or more of thedescribed techniques. An apparatus can include one or more processorsand one or more computer-readable media comprising instructions that,when executed by the one or more processors, cause the one or moreprocessors to perform one or more of the described techniques.

The methods described here may be implemented in software, hardware, ora combination thereof, in different implementations. In addition, theorder of the blocks of the methods may be changed, and various elementsmay be added, reordered, combined, omitted, modified, and the like.Various modifications and changes may be made as would be obvious to aperson skilled in the art having the benefit of this disclosure. Thevarious implementations described here are meant to be illustrative andnot limiting. Many variations, modifications, additions, andimprovements are possible. Accordingly, plural instances may be providedfor components described here as a single instance. Boundaries betweenvarious components, operations and data stores are somewhat arbitrary,and particular operations are illustrated in the context of specificillustrative configurations. Other allocations of functionality areenvisioned and may fall within the scope of claims that follow. Finally,structures and functionality presented as discrete components in theexample configurations may be implemented as a combined structure orcomponent.

The methods described herein can be implemented in circuitry such as oneor more of: integrated circuit, logic circuit, a processor (shared,dedicated, or group) and/or memory (shared, dedicated, or group), anApplication Specific Integrated Circuit (ASIC), a field-programmabledevice (FPD) (e.g., a field-programmable gate array (FPGA), aprogrammable logic device (PLD), a complex PLD (CPLD), a high-capacityPLD (HCPLD), a structured ASIC, or a programmable SoC), digital signalprocessors (DSPs), or some combination thereof. In some implementations,the circuitry may execute one or more software or firmware programs toprovide at least some of the described functionality. The term“circuitry” may also refer to a combination of one or more hardwareelements (or a combination of circuits used in an electrical orelectronic system) with the program code used to carry out thefunctionality of that program code. In these embodiments, thecombination of hardware elements and program code may be referred to asa particular type of circuitry. Circuitry can also include radiocircuitry such as a transmitter, receiver, or a transceiver.

A number of implementations have been described. Nevertheless, it willbe understood that various modifications may be made. Elements of one ormore implementations may be combined, deleted, modified, or supplementedto form further implementations. As yet another example, the logic flowsdepicted in the figures do not require the particular order shown, orsequential order, to achieve desirable results. In addition, other stepsmay be provided, or steps may be eliminated, from the described flows,and other components may be added to, or removed from, the describedsystems. Accordingly, other implementations are within the scope of thefollowing claims.

1. A method comprising: determining, by a User Equipment (UE), aPrecoding Resource Block Group (PRG) size based on a downlink controlinformation (DCI) message that provides scheduling information for aphysical downlink shared channel (PDSCH); receiving, by the UE, a groupof PDSCH transmissions from multiple transmission and reception points(TRPs) that are transmitted in accordance with the DCI message; anddecoding, by the UE, one or more of the PDSCH transmissions based on thePRG size.
 2. The method of claim 1, wherein the PDSCH transmissionscomprise physical resource blocks (PRBs) that are associated withdifferent transmission configuration indicator (TCI) states, wherein themultiple TRPs are respectively associated with the TCI states.
 3. Themethod of claim 2, wherein the TCI states comprise a first TCI state anda second TCI state, wherein the PRBs comprise a first PRB associatedwith a first TCI state and a second PRB associated with a second TCIstate, and wherein determining the PRG size comprises determining if thefirst PRB and the second PRB overlap.
 4. The method of claim 2, whereindetermining the PRG size comprises determining if the PRBs associatedwith the different TCI states are non-overlapping or at least partiallyoverlapping.
 5. The method of claim 4, wherein determining the PRG sizecomprises determining that the PRG size is not wideband if the PRBsassociated with different TCI states are partially overlapping ornon-overlapping.
 6. The method of claim 2, comprising: determining thata precoder for at least one of the PDSCH transmissions is constant orwideband if PRBs associated with different TCI states arenon-overlapping.
 7. (canceled)
 8. The method of claim 2, whereindetermining the PRG size comprises determining if a bundle typeparameter specifies a dynamic bundling attribute, wherein determiningthe PRG size comprises determining if a bundle size set parametercontains two or more bundle size parameters, wherein determining the PRGsize comprises determining if at least a portion of the PRBs arecontiguous.
 9. (canceled)
 10. (canceled)
 11. (canceled)
 12. (canceled)13. An apparatus comprising: one or more processors; circuitryconfigured to receive information comprising a downlink controlinformation (DCI) message that provides scheduling information for aphysical downlink shared channel (PDSCH), and a group of PDSCHtransmissions from multiple transmission and reception points (TRPs)that are transmitted in accordance with the DCI message; and a memorystoring instructions that, when executed by the one or more processors,cause the one or more processors to perform operations comprising:determining a Precoding Resource Block Group (PRG) size based on the DCImessage; and decoding one or more of the PDSCH transmissions based onthe PRG size.
 14. The apparatus of claim 13, wherein the PDSCHtransmissions comprise physical resource blocks (PRBs) that areassociated with different transmission configuration indicator (TCI)states, wherein the multiple TRPs are respectively associated with theTCI states.
 15. The apparatus of claim 14, wherein the TCI statescomprise a first TCI state and a second TCI state, wherein the PRBscomprise a first PRB associated with a first TCI state and a second PRBassociated with a second TCI state, and wherein determining the PRG sizecomprises determining if the first PRB and the second PRB overlap. 16.The apparatus of claim 14, wherein determining the PRG size comprisesdetermining if the PRBs associated with the different TCI states arenon-overlapping or at least partially overlapping.
 17. The apparatus ofclaim 16, wherein determining the PRG size comprises determining thatthe PRG size is not wideband if the PRBs associated with different TCIstates are partially overlapping or non-overlapping.
 18. The apparatusof claim 14, wherein the operations comprise: determining that aprecoder for at least one of the PDSCH transmissions is constant orwideband if PRBs associated with different TCI states arenon-overlapping.
 19. The apparatus of claim 14, wherein the DCI messageis a single DCI message that provides scheduling information for thegroup of PDSCH transmissions.
 20. The apparatus of claim 14, whereindetermining the PRG size comprises determining if a bundle typeparameter specifies a dynamic bundling attribute, wherein determiningthe PRG size comprises determining if a bundle size set parametercontains two or more bundle size parameters, wherein determining the PRGsize comprises determining if at least a portion of the PRBs arecontiguous.
 21. (canceled)
 22. The apparatus of claim 14, wherein theTCI states comprise a first TCI state and a second TCI state, wherein ifthe PRG size is determined as wideband, ┌n_(PRB)/2┐ of the PRBs areassigned to the first TCI state and the remaining └n_(PRB)/2┘ of thePRBs are assigned to the second TCI state, where n_(PRB) is the totalnumber of allocated PRBs for the UE.
 23. The apparatus of claim 14,wherein the PR wherein the TCI states comprise a first TCI state and asecond TCI state, if the PRG size is determined as subband, the evenPRGs within allocated frequency domain resources are assigned to thefirst TCI state and odd PRGs within the allocated frequency domainresources are assigned to the second TCI state.
 24. The apparatus ofclaim 13, wherein the DCI message comprises two or more DCI messagesthat provide scheduling information for the group of PDSCHtransmissions.
 25. The apparatus of claim 24, wherein the PDSCHtransmissions comprise physical resource blocks (PRBs) that areassociated with different transmission configuration indicator (TCI)states, wherein the multiple TRPs are respectively associated with theTCI states, and wherein determining the PRG size comprises determiningif a bundle type parameter specifies a dynamic bundling attribute. 26.The apparatus of claim 25, wherein determining the PRG size comprises:determining that a PRG size is equal to wideband based on the two ormore DCI messages, wherein determining that the PRG size is equal towideband comprises determining whether a bandwidth of a total number ofPRBs scheduled by the two or more DCI messages is above half of abandwidth of an active bandwidth part.